Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Support Composite Primary Keys Containing BIT Columns (SQL Server)

Answered
Subrahmanya Ganapati Gaonkar User

Customers are unable to sync SQL Server tables where composite primary keys include a column of BIT data type, even when the BIT column is not the sole primary key component. This limitation prevents ingestion of valid production tables that follow standard SQL Server modeling practices.

Example PK structure from customer table:

PRIMARY KEY (col1 INT, col2 BIT, col3 INT)

Fivetran currently blocks syncing due to the presence of a BIT column in the primary key, even though the PK as a whole is still valid and ensures row-level uniqueness.

Does the product have any plans to implement the same in the near future? Please share the ETA.

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Rean Fivetranner

    Hi Ganapati,

    Thank you for flagging this and for sharing the customer’s feedback.

    To help us better understand the scope and urgency of this issue, could you share more details about the replication method these customers are using (e.g. Teleport, CT, CDC, Binary Log Reader)? It would also be helpful to know which customers have raised this request.

    We don’t yet have an ETA to share for support of this scenario, but I’ll bring this feedback to our engineering teams for review. Every example helps us prioritize improvements more effectively.

    Thanks again for surfacing this.

    Best, 
    Rean Rodrigues, Product Manager - Databases