We have been struggling to uninstall the Cumulative Update package 7 on a development SQL Server! As it is an important aspect of installation to rollback or to have a backout plan tested if you are performing any kind of installation against your Production Server, not to mention its a best practice...
Secured by default, secured by design is the buzzword and catchy stuff for any Enterprise IT administrators. Then it comes about standards and policies to follow such as ISO , with the recent threats (last 10 years) and vulnerabilities within IT world it is most important factor you need to follow as...
IN continuation to the post Rollback_of_CumulativeUpdate-hotfix-ServicePack I was asked about any procedure or steps on installing Cumulative update package 7 for SQL Server 2005 Service Pack 2 on Active node SQL 2005 cluster. The simple answer is all of such hotfix/Service Pack/Cumulative Update packages...
To cut the long story short, during a recent implementation of Cumulative Update 6 and 7 on a particular 'application domain' server we have had major application issues due to a mix up of application code & these SQL cumulative update fixes. Actually this server was not under our support...
Here is the hot news, SQL Server Global Release Services (GRS) has revised their schedule of releasing Service Packs for SQL Server product by stating ' changed approach to Service Packs '. Now the big question how far you can stretch in deploying these service pack releases within your Enterprise...