Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2026 01:58 AM
Hi @cvh,
Having done some research, I have found that for SQL Server CT, Lakeflow expects the following (per DB/catalog)..
- Utility objects at version 1.5: dbo.lakeflowUtilityVersion_1_5() = '1.5'.
- CT DDL objects present in the same database as the CT tables:
- Table: dbo.lakeflowDdlAudit_1_5
- Database DDL trigger: lakeflowDdlAuditTrigger_1_5 (enabled)
- The ingestion user can read from dbo.lakeflowDdlAudit_1_5.
- The DDL trigger is actually writing rows for CT tables (i.e., DDL is being captured).
If any of these fail, the gateway reports INGESTION_GATEWAY_DDL_OBJECTS_MISSING and logs ddlCaptureNotEnabledTables.
Does your setup meet all the above requirements? Do you know how to check these, or do you need help with that?
If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.
Regards,
Ashwin | Delivery Solution Architect @ Databricks
Helping you build and scale the Data Intelligence Platform.
***Opinions are my own***
Ashwin | Delivery Solution Architect @ Databricks
Helping you build and scale the Data Intelligence Platform.
***Opinions are my own***