- 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.
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.
- 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.
Cumulative update information
Cumulative Update 2 for SQL Server 2012 SP1The 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:
Cumulative update 5 for SQL Server 2012The 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:
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.
Article ID: 2769673 - Last Review: Jan 24, 2013 - Revision: 1