August 7, 2009 at 10:06 am
We are planning the SP3 upgrade to our SQL Server 2005 development servers next week and trying to coordinate local Management Studio installations for our developers. The users with Management Studio will be connecting to the upgraded development servers as well as test and production servers which will not yet be upgraded to SP3.
If we upgrade the local installations for our developers, is SP3 backward-compatable with SP2 SQL Server installations? We may not be upgrading our test and production environments for some time, since we want to ensure no issues on the development servers first.
Are there any known issues with using both SP2 and SP3 servers accessed from local Management Studio installations running SP3 (or vice-versa?)
Thanks for any advice provided.
Kay
August 7, 2009 at 10:11 am
August 10, 2009 at 12:28 pm
As an additional aspect of the upgrade question, there has been some debate in our office as to whether it would be more beneficial to continue on the SP2 path, installing the latest hotfix to SP2 rather than upgrading to the full SP3 release and subsequent fixes.
Can any one offer a compelling reason to choose one path over the other? There are no fixes in the SP3 cumulative releases 1-4 that we are waiting for.
Would really appreciate some guidance from the experts!
Thanks,
Kay
August 10, 2009 at 1:34 pm
The only compelling reason I can think of is the fact that SP3 is a rollup of the changes and fixes made since SP2. That includes the cumulative updates as well as additional fixes not corrected in a specific cumulative update.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply