Symptoms
Consider the following scenario:
-
You create a publication that has column filters from a publication database in an instance of SQL Server 2005.
-
You restore the database backup of the publication database to an instance of SQL Server 2012, 2014 or 2016.
-
The child package contains a connection string that is specified by an expression.
-
You keep the replications settings, for example, by using the KEEP_REPLICATION option in a RESTORE statement.
In this scenario, the replication doesn't work in SQL Server 2012, 2014 or 2016.
Cause
This issue occurs because the length of article columns objects is retrieved from the table metadata which is two bytes for SQL Server 2005 and four bytes for SQL Server 2012, 2014 and 2016. Because of this, when you try to insert the article column ids into this object, it copies the first two bytes leaving the initial garbage values as is.
Resolution
This problem was fixed in the following cumulative updates for SQL Server:
Cumulative Update 2 for SQL Server 2016 SP1
Cumulative Update 4 for SQL Server 2016
Cumulative update 3 for SQL Server 2014 SP2
Cumulative Update 10 for SQL Server 2014 SP1
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Latest cumulative update for SQL Server 2016
Latest cumulative update for SQL Server 2014 SP1/SP2
Latest cumulative update for SQL Server 2012
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology Microsoft uses to describe software updates.
