Google Cloud SQL Server (Edge)

Last updated on Jan 22, 2026

Edge Pipeline is now available for Public Review. You can explore and evaluate its features and share your feedback.

Google Cloud SQL Server is a fully-managed database service that helps you set up, maintain, manage, and administer your SQL Server relational databases on Google Cloud Platform.

You can ingest data from your Google Cloud SQL Server database using Hevo Pipelines and replicate it to a Destination of your choice.


Data Type Mapping

Hevo maps the SQL Server Source data type internally to a unified data type, referred to as the Hevo Data Type, in the table below. This data type is used to represent the Source data from all supported data types in a lossless manner.

The following table lists the supported SQL Server data types and the corresponding Hevo data type to which they are mapped:

SQL Server Data Type Hevo Data Type
- CHAR
- VARCHAR
- TEXT
- NCHAR
- NVARCHAR
- NTEXT
- XML
- UNIQUEIDENTIFIER
- GEOMETRY
- GEOGRAPHY
- HIERARCHYID
- SQL_VARIANT
VARCHAR
- DATETIMEOFFSET TIMESTAMPTZ
- DATETIME
- SMALLDATETIME
- DATETIME2
TIMESTAMP
- TIME TIME
- TINYINT
- SMALLINT
SHORT
- BIGINT LONG
- INT INTEGER
- REAL FLOAT
- FLOAT DOUBLE
- NUMERIC
- DECIMAL
- MONEY
- SMALLMONEY
DECIMAL
- DATE DATE
- BINARY
- VARBINARY
- IMAGE
- TIMESTAMP
BYTEARRAY
- BIT BOOLEAN

At this time, the following SQL Server data types are not supported by Hevo:

  • CURSOR

  • VECTOR

  • ROWVERSION

  • TABLE

  • Any other data type not listed in the table above.

Note: If any of the Source objects contain data types that are not supported by Hevo, the corresponding fields are marked as unsupported during object configuration in the Pipeline.


Source Considerations

  • When a record is updated multiple times between two consecutive data ingestion runs, Change Tracking captures only the latest update made to the record. As a result, Hevo ingests only the latest record at the time of ingestion, which can lead to the loss of any updates that occurred between the previous ingestion and the current one.

  • By default, SQL Server uses a case-insensitive collation. This means that values such as tables, Tables, and TABLES are treated as identical by the server.

    To differentiate between cases in your data, change the collation to case-sensitive.

  • For a CDC-enabled database, SQL Server creates change tables in the cdc schema using the database default collation. If columns in the Source table use different collations, CDC does not preserve the column-level collation in the change tables.

    As Hevo replicates data from the cdc schema, this behavior may result in data inconsistencies between the Source and Destination data, especially for string values. Therefore, it is recommended to set the same collation for the database and columns.

  • SQL Server does not log values from computed columns in the CDC change tables. As a result, Hevo can ingest only historical data from such columns; any incremental updates are not captured.


Limitations

  • Hevo does not support data replication from temporary tables and views.

  • Hevo does not set the metadata column __hevo__marked_deleted to True for data deleted from the Source table using the TRUNCATE command. This action could result in a data mismatch between the Source and Destination tables.

  • Hevo does not support ingesting data using Change Data Capture (CDC) from a single-user SQL Server database.

  • If you modify the tracking mechanism for a table from Change Tracking to CDC or vice versa, resync the table to ensure data consistency


Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Jan-23-2026 NA Updated the page for SQL Server CDC support:
-   Added the following sections: Enable Change Data Capture, Grant privileges for Change Data Capture, and
-   Updated the following sections: Prerequisites, Enable Change Tracking, Configure Google Cloud SQL Server as a Source in your Pipeline Source Considerations, Limitations.

Tell us what went wrong