August 22, 2012 at 10:37 am
Hello -
I have an application that is currently on a SQL Server 2008 instance I'll call instance A. That department wants to upgrade the application and wouldn't you know it SQL Server 2008 is not supported (a surprise to me). 2008 R2 and SQL Server 2012 are supported.
On this server also sits another instance of SQL 2008 I'll call instance B. So I don't want to take the chance of crashing those apps on instance B I will not upgrade instance A to 2008 R2 and affect the common files. But instead will install another instance of 2008 R2 so the common files will not be affected from instance B. I hope that made sense.
There is limited space so restoring the database to the new R2 instance is out of the question. Do you know issues or concerns with detaching and reattach the db to the new instance? Basically redirecting the data files from the 2008 to 2008 R2. What scripts besides running sp_removedbreplication would I need to run or can recommend?
Regards,
David
August 23, 2012 at 12:39 am
david.ostrander (8/22/2012)
Hello -I have an application that is currently on a SQL Server 2008 instance I'll call instance A. That department wants to upgrade the application and wouldn't you know it SQL Server 2008 is not supported (a surprise to me). 2008 R2 and SQL Server 2012 are supported.
On this server also sits another instance of SQL 2008 I'll call instance B. So I don't want to take the chance of crashing those apps on instance B I will not upgrade instance A to 2008 R2 and affect the common files. But instead will install another instance of 2008 R2 so the common files will not be affected from instance B. I hope that made sense.
There is limited space so restoring the database to the new R2 instance is out of the question. Do you know issues or concerns with detaching and reattach the db to the new instance? Basically redirecting the data files from the 2008 to 2008 R2. What scripts besides running sp_removedbreplication would I need to run or can recommend?
Regards,
David
You did not mention what do you have in instance A. From the thread I assume you have replication.
Any logshipping /mirroring. And what kind of replication you have. Please post those kind of information.
Its very simple for moving the user databases to another instance. All you need to do is specify the new locations for the data files for the new instance.
Please let me know if you are expecting any information.
August 23, 2012 at 1:44 am
There is limited space so restoring the database to the new R2 instance is out of the question. Do you know issues or concerns with detaching and reattach the db to the new instance? Basically redirecting the data files from the 2008 to 2008 R2. What scripts besides running sp_removedbreplication would I need to run or can recommend?
Just ensure before detach, the stats are updated and you have fresh full backup.
The attach method will automatically update the user database as per new build.
Also after attach,
1) Dont forget to change the compatibility of database.
2) update stats.
3) Re-Map SQL Login/s
4) take fresh backup
----------
Ashish
August 23, 2012 at 7:12 am
You did not mention what do you have in instance A. From the thread I assume you have replication.
Any logshipping /mirroring. And what kind of replication you have.
Instance A is a Team Foundation Server with 9 databases. Domain Service accounts and NT Service accounts are used for logLoginso replication or logshipping/mirroring. Only Trans Log backups and full database backups.
Was there more info I should provide?
Thanks,
David
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply