We are experiencing an issue with Datastream, when replicating SQL Server (Cloud SQL) tables that have formally defined primary keys. The error message indicates that the primary key row is not being included, suggesting a row-selection problem.
However, our investigation shows that the root cause is that Datastream fails to correctly map only tables with formal primary key definitions in the database.
Details
- Affected Tables: Tables with formally defined primary keys in SQL Server fail to map correctly.
- Working Cases: Tables without a formally defined primary key are processed correctly, and the system automatically replaces spaces in column names with underscores.
Impact
- Misleading error message indicating that primary key rows are not selected.
- Inconsistent mapping behavior based on the presence of a formal primary key,
- We are blocked from Datastream & BigQuery configuration, since these tables fail in Datastream.
Request
Please investigate the parsing and mapping issue and provide guidance on a resolution or workaround. We can supply additional logs and details if needed.
Thank you,
LinkedIn
Twitter
