@kapa.ai

com.microsoft.sqlserver.jdbc.SQLServerException: Column '_ab_cdc_deleted_at' in table 'dbo.DB01_STORETEMP' is of a type that is invalid for use as a key column in an index.

Is this still an issue with the 4.3.5 MS SQL Destination Connector?

The knowledge sources confirm this error for the MSSQL destination connector, but only specify it for version 2.2.9, where

_ab_cdc_updated_at

and

_ab_cdc_deleted_at

are created as

VARCHAR(MAX)

, which cannot be used in indexes in SQL Server. [MSSQL index issue] There is no information in the provided sources indicating whether this has been fixed or changed in later versions such as 4.3.5. Because of that, I cannot say with confidence whether the issue still exists in 4.3.5 based on these documents alone. From the same issue, a known workaround is to manually alter those columns to an index-compatible type (e.g.

VARCHAR(200–250)

) and then re-run the sync. [MSSQL index issue] To know definitively for 4.3.5, you’d need to either: • Check the schema that the connector creates for

_ab_cdc_*

columns in your environment, or • Check the current release notes / open issues for

destination-mssql

beyond what’s included here. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai I'm actually using this image airbyte/destination-mssql:2.2.15

The knowledge sources only document this specific issue for destination-mssql 2.2.9, where

_ab_cdc_updated_at

and

_ab_cdc_deleted_at

are created as

VARCHAR(MAX)

, which is invalid as an index key type in SQL Server. [MSSQL index issue] For 2.2.15, the provided changelog only mentions CDK upgrades and internal fixes; it does not explicitly state any change to the types of

_ab_cdc_*

columns or to the index-creation logic. [MSSQL changelog] Because of that, I cannot confirm from these sources whether the bug is fixed in 2.2.15. Given your error message matches the one in the issue, it is likely you are still hitting the same behavior. The documented workaround remains:

ALTER TABLE dbo.DB01_STORETEMP
  ALTER COLUMN _ab_cdc_deleted_at VARCHAR(250) NULL;

ALTER TABLE dbo.DB01_STORETEMP
  ALTER COLUMN _ab_cdc_updated_at VARCHAR(250) NULL;

Then re-run the sync so the index can be created on these now index-compatible columns. [MSSQL index issue] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.