Don’t let change pass you by! Get started with Change Tracking in your SQL Database | Data Exposed

Many database administrators ask questions like "What rows have changed for a table?" and "How has that row changed in that table?". Change Tracking is a lightweight solution built right into the SQL Database that gives you the ability to query for data that has changed over time. In this episode of Data Exposed, join Anna Hoffman and Brian Spendolini as we explore this powerful feature of the database. Learn how to enable Change Tracking in your database, what are the best uses cases, and how it can save you massive amounts of time and effort over developing custom, one-off solutions.

0:00 Introduction
1:36 What is change tracking in Azure SQL Database
3:57 Why use change tracking
4:44 How and where can I use change tracking
5:58 How and why can I use change tracking
7:18 Demo
13:28 Getting started

✔️ Resources:
About Change Tracking:
Change Tracking Functions:
Data replication on Azure SQL Databases:

📌 Let's connect:

🔔 Subscribe to our channels for even more SQL tips:

#AzureSQL #AzureSQLDatabase #ChangeTracking

[DB-sfhy]

Very good idea to also include topics about features that are not new.

[gaberice]

Thank you, good explanation and examples. I use it to track changes in my organisation where a third party data mart app provides incremental updates to one of our DBs.

[Astral]

Thank you, that was very helpful. Finally allowed me to understand what I was doing wrong in following examples on Microsoft learning pages. (This damned 'ColumnId', which is a string constant, unlike the other parameters in the COLUMNPROPERTY, ugh...)

[Astral]

Also it looks like there is a bug in Change tracking. Updating same row with several updates keeps the same (single) SYS_CHANGE_VERSION for all of the updates, even if you run updates separately! Which makes it impossible to trigger processing for only that one column that has just been updated.