Microsoft distributes Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release.
Symptoms
Consider the following scenario:
-
You use the Microsoft SQL Server 2012 Change Data Capture Service for Oracle by Attunity to generate a deployment script for a capture instance.
-
You try to use the script to deploy the capture instance.
In this scenario, the length of a variable width data type column is doubled in SQL Server tables that are created in the script.
For example, if you try to track changes on a VARCHAR2(10) column in an Oracle table, then the corresponding column in the SQL Server table is NVARCHAR(20) in the deployment script.
Notes
-
If the length of a column in an Oracle table is greater than 2000 bytes when you run the deployment script, then the deployment fails. This occurs because some invalid columns are created by the deployment script. For example, if the column is VARCHAR(2001), then an invalid NVARCHAR(4002) column is created in the script.
-
The unexpected length of the data type may prevent the user from creating indexes on the columns. This occurs because the maximum size of index keys is reached.
-
The length of the data type may cause performance issues for Microsoft SQL Server Integration Services (SSIS).
-
This issue only occurs in the generated script. Therefore, the lengths of columns are displayed accurately in the designer UI.
Resolution
Cumulative update information
Cumulative Update 2 for SQL Server 2012 SP1
The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2790947 Cumulative update package 2 for SQL Server 2012 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 SP1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
Cumulative update 5 for SQL Server 2012
The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2777772 Cumulative update package 5 for SQL Server 2012Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
