January 20, 2011 at 9:46 am
never had a problem
our QA is almost always on a later build than production and we restore databases there. we also have a process to sync databases on a SAN from x64 servers running a very recent SQL build to a windows 2000 server running an earlier version of sql 2005
January 20, 2011 at 10:04 am
Usually you should avoid going backwards when at all possible. One issue you may come across is if you apply SP2, enable 15K partitions, then try to move that database to anything < SP2 ... good luck. That's a pretty obscure scenario, but other cases exist, such as back in 2005 if you applied SP2 and started using the enhanced metadata functions, your code would break if you deploy the same code to SP1 or RTM.
I don't recall if I've ever tried detaching a database from SP2 and attaching it to SP1... I think I always live by my first statement above.
April 1, 2011 at 1:50 pm
Where does R2 fit in this list? I thought if you were installing new systems you should be using R2. Although I have vendors that only go as far as SP1. I have tested several on R2 in a pilot test but technically not supported by vendor since they say SP1.
So I am unsure if I should go SP1 or R2 in general. I have some 12 servers that I am hoping to update this year and want to be consistant as best as I can.
I really like this build list and have been checking it every now and then.
April 1, 2011 at 2:08 pm
April 1, 2011 at 2:52 pm
Thank you, that does provide a good bit of information. I thought a spot on the 2008 build list would show at what point R2 was started. Like does R2 include SP1 or off the base with no CU or SP. If I understand it is a new release but I don't see much if anything that explains where it spins off the main version.
April 1, 2011 at 3:09 pm
matthew.stone (4/1/2011)
Thank you, that does provide a good bit of information. I thought a spot on the 2008 build list would show at what point R2 was started. Like does R2 include SP1 or off the base with no CU or SP. If I understand it is a new release but I don't see much if anything that explains where it spins off the main version.
Roughly, you can consider SQL 2008 R2 RTM as spun off from SQL 2008 SP1 CU4. SQL 2008 R2 CU1 brings that up to parity with SQL 2008 SP1 CU 7. The intro text for R2 CU1 gives you the clue:
Cumulative Update 1 for Microsoft SQL Server 2008 R2 RTM contains only hotfixes that were released in Cumulative Update 5, 6, and 7 for SQL Server 2008 Service Pack 1 (SP1). Cumulative Update 1 for SQL 2008 R2 RTM is only intended as a post-RTM rollup for Cumulative Update 5-7 for the release version of SQL Server 2008 SP1 customers who plan to upgrade to SQL Server 2008 R2 and still keep the hotfixes from Cumulative Update 5-7 for the release version of SQL Server 2008 SP1. No new hotfixes have been included in this cumulative update.
However, R2 is not just a rollup of fixes. See the What's New doument at http://msdn.microsoft.com/en-us/library/bb500435.aspx for more information.
April 21, 2011 at 3:28 am
someone forgot to update the download xls :blink:
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
May 18, 2011 at 6:41 am
Hi all
The original article will be updated when next CU comes?
Regards
Rodrigo Moraes
May 18, 2011 at 6:50 am
matthew.stone (4/1/2011)
Thank you, that does provide a good bit of information. I thought a spot on the 2008 build list would show at what point R2 was started. Like does R2 include SP1 or off the base with no CU or SP. If I understand it is a new release but I don't see much if anything that explains where it spins off the main version.
Edit : Hadn't seen the 2nd page. Sorry if repost.
Good idea. If you still need that info you could look at the link in the post right before yours. That'll give you the R2 history so you can guesstimate at it. You can also think of 2008 R2 as sql 10.5. A little like sql 6 and 6.5. There are defenite improvements, but not enough for a new major version.
May 18, 2011 at 7:13 am
Thank you, Unfortunatly I have to stick with SQL 2008 SP1 for the majority and maybe 1-2 R2 for specific approved applications. To many vendors do not mention R2 as a accepted version. If only I could delay the SQL upgrade a few more months to hound the vendors into testing/approving :). They will probably approve the day after I move the databases to SP1 :).
May 21, 2011 at 6:46 am
Hi Steve,
Thanks for the updated article.
For me, I have also used this to find the correct version.
SELECT SERVERPROPERTY('productversion')
10.50.1600.1
Kash
Instructor
SQL Server Tutorials
September 26, 2011 at 8:44 am
Hi, Steve,
The SQL 2008 build list has something wrong. The current CU is 6, not CU4, and seems you missed CU5, which is 10.0.4316.
October 16, 2011 at 6:21 pm
SP3 = 10.0.5500
October 19, 2011 at 1:47 pm
I have a client on R2 so:
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.0 <X64> (Build 6002: Service Pack 2) (Hypervisor)
The backup won't restore onto my SP3 box
Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (X64) Sep 21 2011 22:45:45 Copyright (c) 1988-2008 Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
How can I get around this?
ATBCharles Kincaid
October 19, 2011 at 7:28 pm
Charles Kincaid (10/19/2011)
I have a client on R2 so:Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.0 <X64> (Build 6002: Service Pack 2) (Hypervisor)
The backup won't restore onto my SP3 box
Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (X64) Sep 21 2011 22:45:45 Copyright (c) 1988-2008 Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
How can I get around this?
Please start a new thread.
And the short answer is you can't restore down from an upper version.
Viewing 15 posts - 46 through 60 (of 75 total)
You must be logged in to reply to this topic. Login to reply