Comments on: SQL Server security bulletins http://paulduffett.wordpress.com/2008/09/29/sql-server-security-bulletins/ The ramblings of a mad man Wed, 08 Oct 2008 16:54:46 +0000 http://wordpress.com/ hourly 1 By: paulduffett http://paulduffett.wordpress.com/2008/09/29/sql-server-security-bulletins/#comment-4 paulduffett Wed, 08 Oct 2008 16:46:24 +0000 http://paulduffett.wordpress.com/?p=43#comment-4 Hi Don, Thanks for your comments, it's good to know that someone is actually reading this stuff. You're quite right that you can just go with SP4 and leave it at 2050, that's the GDR approach and we've gone with that on our new builds. The problem is when you've got existing boxes at a higher patch leve. In our case we were putting 2187 on our boxes to fix a particular issue (which escapes me at this moment in time) so we had no choice but to go up to build level 2273. So in short, yes, new builds should be SP4 + 2050. Hope that makes sense Paul Hi Don,

Thanks for your comments, it’s good to know that someone is actually reading this stuff. You’re quite right that you can just go with SP4 and leave it at 2050, that’s the GDR approach and we’ve gone with that on our new builds. The problem is when you’ve got existing boxes at a higher patch leve. In our case we were putting 2187 on our boxes to fix a particular issue (which escapes me at this moment in time) so we had no choice but to go up to build level 2273.

So in short, yes, new builds should be SP4 + 2050.

Hope that makes sense
Paul

]]> By: Don Cavin http://paulduffett.wordpress.com/2008/09/29/sql-server-security-bulletins/#comment-3 Don Cavin Mon, 06 Oct 2008 12:54:23 +0000 http://paulduffett.wordpress.com/?p=43#comment-3 Paul: The way that I interpret .2250 vs. .2273 is that unless you need to apply every hotfix (and have integration/regression tested) from sp4 to .2273, the only logical choice is to pick .2050 from sp4 and stop right there! Microsoft seems very cavalier about upgrading right from 8.00.2039 to 8.00.2273, but from my experience, I am recommending to my client to go to .2050 and stop! Does my stubborn and conservative position have merit? Thanks, Don Paul:

The way that I interpret .2250 vs. .2273 is that unless you need to apply every hotfix (and have integration/regression tested) from sp4 to .2273, the only logical choice is to pick .2050 from sp4 and stop right there! Microsoft seems very cavalier about upgrading right from 8.00.2039 to 8.00.2273, but from my experience, I am recommending to my client to go to .2050 and stop!

Does my stubborn and conservative position have merit?

Thanks,

Don

]]>