← All updates Databricks Update One-Pager Light version
databricks Platform · Updated Nov 14, 2025

Improved full refresh flow for managed database connectors

Full refresh operations for managed database connectors (like SQL Server) now reduce downtime by delaying the table refresh until after the snapshot is completed.

What it does

Full refresh operations for managed database connectors (like SQL Server) now reduce downtime by delaying the table refresh until after the snapshot is completed. During the snapshot process, destination streaming tables remain available with their existing data. New inserts, deletes, and updates are accumulated but not immediately applied.

Why it matters

Full refresh operations for managed database connectors (like SQL Server) now reduce downtime by delaying the table refresh until after the snapshot is completed.

Key capabilities
table: sourceschema: sourcetable:
table: sourceschema: sourcetable: destinationcatalog: destinationschema…
MONDAY
MONDAY
TUESDAY timezoneid: 'America/LosAngeles'
TUESDAY timezoneid: 'America/LosAngeles'
table: sourceschema: sourcetable:
table: sourceschema: sourcetable: destinationcatalog: destinationschema…
Architecture
Databricks Platform → Platform
In short

Full refresh operations for managed database connectors (like SQL Server) now reduce downtime by delaying the table refresh until after the snapshot is completed. During the snapshot process, destination streaming tables remain available with their existing…

Read the full documentation ↗
Key takeaway
Full refresh operations for managed database connectors (like SQL Server) now reduce downtime by delaying the table refresh until after the snapshot is completed.
2025-11-14-improved-full-refresh-flow-for-managed-database-connectors Generated by the Databricks Updates Agent · browse all updates