Frequently Asked Questions (FAQ) for Change Event Streaming (CES)

Yes. CES is supported in Azure SQL Database starting in November 2025.

Yes. CES relies on reading the transaction log, so the SQL Server database must be configured with the full recovery model.

For CES, Azure Event Hubs usage is billed at standard rates. Ingress and egress charges also apply.

The performance impact depends on your specific workload and configuration. However, CES is expected to have a lower overhead than change data capture (CDC), as there is no writing data back into the database.

The message size is configurable, up to a maximum of 1 MB and should align with the limits of your Azure Event Hubs instance.

Yes. CES ensures reliable ("at least once") message delivery, so the transaction log won't be truncated until events are successfully delivered. If delivery fails, the log grows until the issue is resolved. It's important to maintain the health of CES by monitoring message delivery, errors, and the utilization of the transaction log for databases that have CES enabled.

CES includes the row schema with each event. If a DDL operation modifies the table (such as deleting, renaming, or adding a column), the next DML event reflects the updated schema. CES doesn't emit events for DDL operations themselves.

Yes. CES supports tables with LOB columns. For each table configured for streaming, you can configure whether large objects are included in the streamed events.

No. CES doesn't require a primary key on the table.

Each row affected by an INSERT, UPDATE, or DELETE operation is streamed as a separate event.

Each affected row is streamed as a separate event. Each event includes transaction metadata, so changes from the same transaction can be logically grouped on the destination.

CES only streams from the primary replica. In the event of a failover, CES must be reconfigured on the new primary. You can connect to the primary replica using any method supported by SQL Server, including DNN.

CES supports AMQP and Kafka protocols for Azure Event Hubs. HTTPS isn't supported.

No. CES currently supports only Azure Event Hubs (AMQP and Kafka protocol) as the destination.

It depends on the data source. CES on Azure SQL Database supports Microsoft Entra managed identity to authenticate with Azure Event Hubs, where SQL Server 2025 currently does not support Microsoft Entra for authentication.

No. CES can't be enabled on a database configured with transactional replication.

No. CES can't be enabled on a database enabled with CDC.

No. CES isn't supported with Fabric Mirrored Databases for SQL Server.

If CES is manually stopped, it doesn't resume automatically. You must manually restart CES to continue streaming events. Changes made while CES was stopped won't be captured. Only changes made after CES is restarted will be streamed. CES guarantees at least once delivery. If CES fails to deliver a message, it continues to retry until the message is successfully delivered, or CES is manually stopped. If CES isn't stopped, failed deliveries prevent log truncation until the error condition is resolved, and the message is successfully delivered. If CES is stopped manually, log truncation resumes, and events that occur during the downtime aren't captured.

No. CES currently only streams changes to data that happen after CES is enabled. It doesn't stream data in a table that exists before CES is enabled.

Use the following system views to monitor CES activity:

• sys.dm_change_feed_errors for event delivery errors.
• sys.dm_change_feed_log_scan_sessions for log scan activity.

In SQL Server 2025, you can create CES related XEvent session and get more details on CES activity and potential errors.

  CREATE EVENT SESSION ChangeEventStreaming
  ON SERVER
  ADD EVENT sqlserver.synapse_link_error
  (
  )
  ADD TARGET package0.event_file 
  (SET filename=N'C:\temp\YourSession_Target1.xel');
  GO

xEvent debugging isn't supported for troubleshooting CES in Azure SQL Database.

You can monitor Azure Event Hubs and use associated metrics and logs.

Yes. CES supports up to 4,096 streaming groups, with up to 40,000 tables per group.