Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
MorningZ
Starting Member
44 Posts |
 Posted - 2011-06-26 : 13:07:58
|
| So a year ago, I set up SQL 2008 (non-R2) on our development staging serverAt the time our production database was SQL 2000, so I could take backups from it and restore to the above mentioned SQL '08 with no problemin between I had installed R2 on the development box for our everyday code-against database and set it up as a named instance....So a snapshot of that time:- SQL 2008 non-R2: default instance- SQL 2008 R2: named instanceFew weeks back we finally made the transition in production from SQL2000 to SQL2008 R2Now I have the issue that I cannot take the backups from it and restore to the default instance on the dev server (because it's an older version of SQL trying to read a newer versions backup)What is a good plan of attack to:- Uninstall the non-R2 version of SQL on the development box- Setup a new instance, as the default instance, of R2 on thereAny tips would be appreciated |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
MorningZ
Starting Member
44 Posts |
Posted - 2011-06-27 : 07:10:36
|
| but that would only leave me with one instance.... (i still need two, and both with R2 as the server) |
 |
|
|
nigelrivett
Master Smack Fu Yak Hacker
3385 Posts |
Posted - 2011-06-27 : 07:38:23
|
| Then add another r2 instance?Not sure what the problem is. You have production r2 servers so should have r2 dev servers.I would probably add a new r2 instance and then shut down the v2000 instance when it's no longer needed.==========================================Cursors are useful if you don't know sql.SSIS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
|
|
|
Lining up versions of SQL2008 and SQL2008 R2