Skip to content

Commit 227e00e

Browse files
Fix typo in CES renaming support section
u spelt rong 🫣
1 parent a3b5438 commit 227e00e

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • docs/relational-databases/track-changes/change-event-streaming

docs/relational-databases/track-changes/change-event-streaming/configure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -536,7 +536,7 @@ The following limitations apply when using CES with Azure SQL Database:
536536
- CES doesn't handle schema changes (DDL operations), which means it doesn't emit events for DDL operations. However, DDL operations aren't blocked, so if you execute them, the schema of subsequent DML events reflects the updated table structure. You're expected to gracefully handle events with the updated schema.
537537
- Currently, CES doesn't stream data that exists in a table before CES is enabled. Existing data isn't seeded, or sent as a snapshot, when CES is enabled.
538538
- If a message exceeds the Azure Event Hubs message size limit, the failure is currently only observable through Extended Events. CES xEvents are currently only available in SQL Server 2025, and not Azure SQL Database.
539-
- Renaming tables and columns configuired for CES isn't supported. Renaming a table or column fails. Database renames **are allowed**.
539+
- Renaming tables and columns configured for CES isn't supported. Renaming a table or column fails. Database renames **are allowed**.
540540
- Microsoft Entra authentication for CES isn't currently available in SQL Server 2025.
541541

542542
### Database-level limitations

0 commit comments

Comments
 (0)