Datastreams Bug: Primary Key Mapping Failure on Tables with Formal Definitions

[gmk]

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,

[dawnberdan]

Hi @gmk,

Welcome to Google Cloud Community!

Thank you for providing the details. With this, I suggest filing a bug report with relevant information so that our Engineering Team can look into it. Before filing, please take note on what to expect when opening an issue. You can also check the release notes for any latest updates or new features related to Datastream.

For further clarification, you may reach out to Google Cloud Support for a one-on-one discussion about your issue. Their team has the specialized expertise to diagnose and resolve complex problems effectively.

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.