October 21, 2009 at 3:01 pm
Hello,
I am setting up a test SQL 2005 db server (64-bit, Standard Edition) and am curious to know if there is a recommendation on which service pack to install. Our production servers are at SP2, but I know SP3 is available. Should I install SP3 on test to get a jump on it, or install SP2 so that it will match the current production environment? Or if it depends, what factors should I consider?
Thanks for any help!
-webrunner
-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
October 21, 2009 at 3:21 pm
In general, I setup what's currently in production in both development and test. However, it would be nice to say "I'm xx% complete in my testing of SP3." when someone asks "Why haven't we rolled out SP3 yet?" at the next meeting.
October 21, 2009 at 3:22 pm
SP3 has been out for a while...i guess the best answer is 'it depends'
If your test environment needs to replicate your production environment. In most cases a test environment would need to identically configured to prod then you need stick with SP2... If you have some scope with your test environment then you could apply SP3
I would recommend you look to apply SP3 to at least a dev environment and try to move to it in test and prod.
Gethyn Elliswww.gethynellis.com
October 21, 2009 at 6:23 pm
You must be having an Idea what is that you are trying to achieving by setting up the test Server.
It's a general rule of thumb that your test Server is on the same SQL Server Edition and SP of the production Box (in Your Case SP2) but if you are trying to implement something new that is depending on the SP3 Bug Fixes it's straight forward, Apply SP3.
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
October 22, 2009 at 6:59 am
Thanks for the replies.
I think I'm leaning towards installing SP2 on the test server, since (to complicate things even more) we are moving from SQL 2000 to 2005 and the new test db server is SQL 2005 while the old one was SQL 2000. So I think the testing for the db migration should simulate moving a SQL 2000 db into our current production environment, which is SQL 2005, SP2. We have not yet made plans to install SP3, but I think we can handle that testing separately once we are ready for it.
Thanks again,
webrunner
-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
October 22, 2009 at 7:42 am
I think that is a valid reason to install your test server with SP2.
The migration project is the factor that calls for this decision. !
When testing your migration, try to switch your db to dblevel 90 (sql2005) as soon as possible.
If the SQL2005 Upgrade advisor didn't point you to huge issues, I would even just set the dblevel to 90 right after the restore operation, and have your test team document the issues they encounter.
If the budget is insufficient to fix the outer join issues, ("*=" and "=*"), only then switch it back to 80 and allow upgrade with caution.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
October 22, 2009 at 7:51 am
Thanks for this additional advice!
-webrunner
-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply