Is snapshot replication supported from SQL Server 2017 to SQL Server 2012?
According to Microsoft Documentations:
Backward compatibility is important to understand if you are upgrading, or if you have more than one version of SQL Server in a replication topology.
This link may help you.Replication Backward Compatibility
Related
For instance I have an application that says it supports SQL Server 2005 to SQL Server 2008. If I transfer that database to a SQL Server 2017 machine and set the compatibility mode to 2008, should it behave just the same as if it were really on a SQL Server 2008 box? I know that the compatibility mode does limit the feature set and behaviors to what would be present in SQL Server 2008. So part of me thinks this should work just fine. But another part of me wonders if there may be others things that I am not considering that could potentially be an issue. Does anyone have any experience where this has come back to bite you?
"Upgrade the database to a SQL 2017 server and set the compatibility
mode to 2008 should it behave just the same as if it were really on a
SQL 2008 server"
Yes this is correct.
This also happens to be Microsoft's recommended upgrade process. As per Microsoft, upgrade to the latest version off SQL Server but keep the source database compatability level.
If a full database backup was taken on a older version of SQL server but restore was done on a new version, then the database compatability level is the same as old version unless its not supported on new version. In that case the database compatability level will switch to the lowest supported.
More here and here
Can you create an SQL SERVER 2016 distributer that merges data between a 2008 R2 server to another 2008 R2 server?
Yes.
This is covered in Using Multiple Versions of SQL Server in a Replication Topology:
For all types of replication, the Distributor version must be no
earlier than the Publisher version. (Frequently, the Distributor is
the same instance as the Publisher.)
Since your Distributor version is a later version than your Publisher version, you are good here.
Quick question: can you replicate a database from SQL Server 2012 to 2008 R2?
We currently have a push transactional replication setup from a SQL Server 2008 R2 database (publisher) to another 2008 R2 (subscriber). The publisher is controlled by a partner organisation that we work closely with, but we have little control over their infrastructure (other than the replication).
Our partner is upgrading their infrastructure to SQL Server 2012 - and as such we need to know if we will be forced to upgrade all or part of our solution to 2012 to follow suit.
Do we need to upgrade our subscriber SQL Server to 2012, or can we leave it as 2008 R2 and somehow configure it to subscribe to a 2012 replication?
Any information and/or references would be appreciated. We're in the process of coming up with a migration plan.
You can keep your 2008R2 subscriber, as long as the distributor and the publisher are one and the same instance (and it seems that they are, since you're running a push trans replication). Quote from here:
A Subscriber to a transactional publication can be any version within two versions of the Publisher version. For example: a SQL Server 2005 Publisher can have Subscribers running SQL Server 2005, SQL Server 2008 (including SQL Server 2008 R2), or SQL Server 2012; and a SQL Server 2012 Publisher can have Subscribers running SQL Server 2005, SQL Server 2008 (including SQL Server 2008 R2), or SQL Server 2012.
Probably you will have to reinitialize your subscription once the publisher upgrade is done. it would be preferable to not use any 2012 specific features or even to run the publisher database in 2008 compatibility mode.
2 versions back SQL replication:
8.0 for SQL Server 2000.
9.0 for SQL Server 2005.
10.0 for SQL Server 2008.
10.5 for SQL Server 2008 R2.
11.0 for SQL Server 2012.
12.0 for SQL Server 2014.
13.0 for SQL Server 2016
I have been using SQL Server 2005 Standard and I want to upgrade it to 2008 R2 Standard.
My question is if there may be a problem when I install the 2008 R2 version on top of the existing SQL Server 2005 Standard installation?
Best Regards
Salih Hanifeoglu
Microsoft provides the Microsoft® SQL Server® 2008 R2 Upgrade Advisor utility for this situation.
Per Micorsoft's description: "Upgrade Advisor identifies feature and configuration changes that might affect your upgrade, and it provides links to documentation that describes each identified issue and how to resolve it."
Download available at: http://www.microsoft.com/en-us/download/details.aspx?id=16978
I have an instance of tfs 2008 supported by sql server 2005. I want to change the sql server machine by doing a restore based move. I also want to change the version of sql server to 2008.
I know that i can restore backups from sql 2005 to sql 2008, IN GENERAL, but I don't know if this is a thing that is OK for tfs databases.
I also know that sql server 2008 is supported by tfs 2008, but in this case when I have done an upgrade I am assuming that I should change the database compatibility mode to be "2008".
So, any advice on doing a sql server upgrade for TFS 2008?
Backup databases and report server key
Start downtime
Upgrade SQL2005 to SQL2008; AT will stop working at this step
Apply VS SP1
Apply TFS SP1; AT will work again
Apply SQL2008 SP1
Verify full functionality
End downtime