http://blogs.technet.com/b/sql_server_isv/archive/2010/10/20/hot-fixes-and-cus-and-service-packs-oh-my.aspxIt is often a challenge to keep up with supporting your own applications, let alone changes to the underlying platforms, such as Microsoft SQL Server, that the application supports. In the face of these changing conditions, the only way to ensure thaten-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.technet.com/b/sql_server_isv/archive/2010/10/20/hot-fixes-and-cus-and-service-packs-oh-my.aspx#3365350Tue, 02 Nov 2010 02:13:33 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3365350SQL Server ISV<p>Giuseppe</p> <p>It can sometimes feel like you&#39;re in a constant state of testing flux but staying on-top of patching definitely minimizes the impact of future changes and also helps solidify your change/release process.</p> <p>Glad you enjoyed the article and thanks for reading! :)</p> <p>^CS</p> <div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3365350" width="1" height="1">http://blogs.technet.com/b/sql_server_isv/archive/2010/10/20/hot-fixes-and-cus-and-service-packs-oh-my.aspx#3364771Thu, 28 Oct 2010 23:18:22 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3364771Giuseppe<p>I think re-iterating the ROI for incremental testing is very important, even though there is a cost to an ISV or anyone else for that matter, in determining how often you can test through each phase of hotfix, CU and SP. &nbsp;But you can deduce that the risk is higher if you just wait for a major SP release to first see how your installation and implementation is affected. &nbsp;Good article, thank you.</p> <div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3364771" width="1" height="1">