Historical Data Tracking

SQL Server Change Tracking to Optimize Data Refreshes for Reporting

You’re a developer responsible for maintaining a SQL Server database used to feed data to Power BI. You realize that some tables don’t have a modifiedDate column and some do. Also, you know the data is updated by the application as well as other processes which makes the modifiedDate unreliable. This is because it may not always be updated when data changes. You need a way to track data changes to ensure only changed rows are updated on reports in Power BI.

Think LSNs Are Unique? Think Again - Preventing Data Loss in CDC ETL

When using only an LSN to track which changes you have processed, you can lose data. This article shows how to avoid this problem.

Enables Change Data Capture (CDC) on all user databases

This script loops through all user databases, skips system DBs and any you want to exclude, and enables CDC if it’s not already enabled.

Implementing Change Data Capture

Detaching CDC

CDC and Restores

Restore a Database with CDC Enabled

In this post, I’m going to talk about an issue that I found while restoring a backup of CDC enabled database to different SQL instance. You may receive below warning message that includes information about the cause of the warning, which can help you to resolve the issue.

Getting Started with Change Data Capture – Part 2

The Change Data Capture feature of SQL Server captures DML changes happening on a tracked table. Arshad Ali demonstrates how this feature can be leveraged.

Getting Starting with Change Data Capture (CDC) in SQL Server – Part 1

Starting with SQL Server 2008, two different in-built mechanisms identify DML changes at the source table so that only changed data sets can be considered for data pulled from the source table to load into the data warehouse. These two in-built mechanisms are Change Data Capture (CDC) and Change Tracking (CT).