Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

When will SQL Server Change Tracking origin allow non-numeric primary keys?

I see from the SDC documentation that the SQL Server Change Tracking Origin only allows simple numeric keys.

See https://streamsets.com/documentation/datacollector/latest/help/datacollector/UserGuide/Origins/SQLServerChange.html

The origin can process data from tables with simple numeric primary keys. The origin cannot process data from tables with compound or non-numeric primary keys.

This is a very severe limitation. I am looking to stream changes from a SQL Server database that uses the uniqueidentifier (guid) data type as it's primary key. Is there anything on your roadmap to enhance this origin any time soon? I can see tickets on JIRA that suggest there might be. E.g. https://issues.streamsets.com/browse/SDC-9417. Any update on this?

Many thanks

When will SQL Server Change Tracking origin allow non-numeric primary keys?

I see from the SDC documentation that the SQL Server Change Tracking Origin only allows simple numeric keys.

See https://streamsets.com/documentation/datacollector/latest/help/datacollector/UserGuide/Origins/SQLServerChange.html

The origin can process data from tables with simple numeric primary keys. The origin cannot process data from tables with compound or non-numeric primary keys.

This is a very severe limitation. I am looking to stream changes from a SQL Server database that uses the uniqueidentifier (guid) data type as for it's primary key. keys. Is there anything on your roadmap to enhance this origin any time soon? I can see tickets on JIRA that suggest there might be. E.g. https://issues.streamsets.com/browse/SDC-9417. Any update on this?

Many thanks