March 9, 2015 at 4:11 am
Hi All,
Looking for some guidance on server migration. We are moving from old h/w to new h/w. i.e. from sql 2008 r2 to sql 2014 RTM. As a result we are planning to move databases and other objects to new server.
I can move jobs,linked servers, logins,db mail configuration,alerts and operators. However, my problem is, how can we move the log shipping and replication. I mean, on old sql server, some db's are acting as primary server for log shipping. At the same time, it also acting as local distribution(it is both Publisher + Distributor).
As I am only one who has to manage the db servers, am trying to see how to do migration in such a scenario.
Looking forward for valuable suggestions before I can go for migration.
What all needs to be considered before and after migration in my scenario.
Thanks in advance.
March 15, 2015 at 9:22 pm
vsamantha35 (3/9/2015)
Hi All,Looking for some guidance on server migration. We are moving from old h/w to new h/w. i.e. from sql 2008 r2 to sql 2014 RTM. As a result we are planning to move databases and other objects to new server.
I can move jobs,linked servers, logins,db mail configuration,alerts and operators. However, my problem is, how can we move the log shipping and replication. I mean, on old sql server, some db's are acting as primary server for log shipping. At the same time, it also acting as local distribution(it is both Publisher + Distributor).
As I am only one who has to manage the db servers, am trying to see how to do migration in such a scenario.
Looking forward for valuable suggestions before I can go for migration.
What all needs to be considered before and after migration in my scenario.
Thanks in advance.
The first thing that comes to mind is issues with being on a new version of SQL Server and trying to Log Ship to an older version. Because you are doing restore operations with Log Shipping, I doubt you could have a secondary on Log Shipping be on a version of SQL Server that is older than you're primary. You could Log Ship up form your current 2008R2 to your new 2014 instance as a way to do the migration, but then making the 2014 the Primary in Log Shipping could be problematic.
As far as Replication goes, I have used a 2005 machine as a Publisher and a 2012 for the Distributor with a 2008R2 box as a subscriber. I think the rule there is that the Distributor has to be on a version that is at least as new as the Publisher.
Another thing I have seen be an issue with 2014 is the new cardinality estimator. It can change the query plans and you can end up with queries and stored procs that are suddenly performing more slowly than they used to. You can go back to the old cardinality estimator with some changes to your database compatibility mode.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply