KB2970137 - FIX: Instance ID is different in related system tables after you register a database as a DAC in SQL Server 2014

Applies To
SQL Server 2014 Developer - duplicate (do not use) SQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Standard - duplicate (do not use)

Symptoms

Assume that you register a Microsoft SQL Server 2014 database as a data-tier application (DAC) in SQL Server Management Studio (SSMS). The instance ID for the new DAC package (DACPAC) is different in the sysdac_history_internal and sysdac_instances_internal system tables after you register.

Note Both tables should have new records that have metadata for the newly registered DACPAC. The instance ID in both tables should be the same, so that you can join the two tables to track history for the different DACPAC.

Resolution

The issue was first fixed in the following cumulative update of SQL Server.

Cumulative Update 2 for SQL Server 2014 /en-us/help/2967546

About cumulative updates for SQL Server

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:

      

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.