May 19, 2014 at 11:37 am
We are planning to perform side by side upgrade of our Prod sql server from sql server 2008 to sql server 2014. Management team is requesting to keep two environments in sync for sometime, so that it would be easy to rollback or revert to old environment if we encounter any major issue. I am thinking of setting up replication with sync option replication support only. Is there any other possible solutions available as backup doesn't work over here in order to setup log shipping from 2014 to 2008. Our database size is >1TB Please advise.
May 19, 2014 at 3:37 pm
Why doesn't backup work?
Because my other suggestion is mirroring and that requires a backup and restore as well.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 20, 2014 at 8:22 am
As once the database has been migrated to 2014- can i take the backup of 2014 database and restore to 2008?
May 20, 2014 at 1:15 pm
muthyala_51 (5/20/2014)
As once the database has been migrated to 2014- can i take the backup of 2014 database and restore to 2008?
No. You can never restore a database down in version. That's always been the case.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 20, 2014 at 1:40 pm
If you are pondering the replication route remember every single table HAS to have a primary key in order for it to be replicated.
May 23, 2014 at 8:49 am
muthyala_51 (5/19/2014)
We are planning to perform side by side upgrade of our Prod sql server from sql server 2008 to sql server 2014. Management team is requesting to keep two environments in sync for sometime, so that it would be easy to rollback or revert to old environment if we encounter any major issue. I am thinking of setting up replication with sync option replication support only. Is there any other possible solutions available as backup doesn't work over here in order to setup log shipping from 2014 to 2008. Our database size is >1TB Please advise.
I've done this myself at work using Mirroring, like Grant indicated. But it is a one way route. You can't go back via Mirror due the differences in version.
You have no other choice here because we are dealing with two different versions of SQL.
The key here is testing. Restore the database on the SQL 2014 box, point your app against that new SQL instance and test. Test again, and test more. And when you are done with testing, test again. There is no shortcut here for testing and even with enough testing, you will find pieces of code that need to be changed once you go live. So going back is not usually an option.
Give app team a deadline, let's say a week? But be clear that moving back means losing some work, usually not an option.
May 24, 2014 at 6:39 am
Markus (5/20/2014)
If you are pondering the replication route remember every single table HAS to have a primary key in order for it to be replicated.
You can use Snapshot replication for tables that do not have primary keys. Snapshot basically copies the entire table and replaces it at the target, so I used it for smaller, more static tables.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply