|
We have 2 database servers; one is our production database server and the other is our test database server. I do my best to make sure that the database schema is identical between the two, and in doing so I noticed that the test database server is at service pack 3 for SQL Server 2005, whereas our production database server is at SP2 for SQL Server 2005. When SP3 came out I remember there being some discussion of some changes to some data types (if memory serves), but I don't think there was much in the way of major changes which would likely negatively impact a business environment which does rather run-of-the-mill type of data actions. So, is there really anything I need to worry about, when considering the possibility of moving our production database server to SP3?
(comments are locked)
|
|
MSDN is the best place to check the details http://msdn.microsoft.com/en-gb/library/dd353312(SQL.90).aspx
(comments are locked)
|
|
As well as research like Fatherjack has suggested, the best way to see if a SP has an affect on your system is to apply it to a test server and, well, test. It seems that you may have, even if somewhat by accident than design, already done this as you say your TEST server is on SP3. Service Packs don't tend to have changes in them like new or removed or fundamentally changed data types - that's more version level - unless there was a bug fix or some other slight change. But that's where testing would come in. The thing to remember is when you are ready to apply the service pack is backup and verify. And not just your user databases, but system ones (master, model, msdb) too. As Grant says, you can't be paranoid enough.
(comments are locked)
|
