SQL Server 2008: Change Data Capture (CDC)

UPDATE!!!
I received a question via email about "Where is the sys.sp_cdc_enable_table_change_data_capture_internal located?"...
The awnser is that its contained in the Resource database along with several other '_internal' CDC objects. If your curious about how to view the Resources database in sql 2005 (or 2008) you can see this article http://www.myitcommunity.com/articles/18/view.asp?id=9138 .
Cheers!
Derek
------------------------------------------------------------------------------------------------
Introduction
One of SQL Server 2008's biggest BI features being touted is Change Data Capture (CDC). CDC is basically suppose to be a built-in solution to the old-age practice in ETL solutions of identifying and using change identifiers columns in source systems. I have now spent a fair amount of time using this feature and more importantly how to leverage it inside of SSIS packages for incremental ETL solutions. My work here has been to prepare for an upcoming demonstration of CDC in SSIS. This post/Q&A is a brief summary of my findings thus far...
 
*CDC is being positioned as the 'design of choice' for SQL Server 2008+ OLTP database servers for exposing changed relational data for data warehousing consumption purposes.
 
What is Change Data Capture (CDC)?
CDC records (or captures) DML activity on designated tables. CDC works by scanning the transaction log for a designated table's 'captured columns' whose content has changed and then making those changes available for data syncronizing purposes in a relational format. As you can see this feature in entrenched in transaction log architecture and thus alot of the metadata in CDC is related around the concept of a Log Sequence Number (LSN).
 
So whats a LSN?
Here is the definition of a LSN per Books Online: "Every record in the Microsoft SQL Server transaction log is uniquely identified by a log sequence number (LSN). LSNs are ordered such that if LSN2 is greater than LSN1, the change described by the log record referred to by LSN2 occurred after the change described by the log record LSN. "
 
How do I get CDC?
CDC is a feature of SQL Server 2008 Enterprise, Developer, and Evaluation editions.
 
What are the target applications or consumers of the CDC technology?
ETL Solutions are the most common, however any data consuming application that requires syncronizing data could benefit from the technology.
 
Is CDC configurable via a UI or just TSQL?
As of this time, just TSQL.
 
How do you configure CDC?
  1. Enable CDC for a database
    1. Enables the current database via the USE statement *select is_cdc_enabled from sys.databases where [name] = 'AdventureWorks' to determine if DB is allready enabled *Also note that when you do this all of the below system objects get created in the selected database
  2. Enable CDC for a given table and it's selected columns
    1. Specify the captured table's schema, name, database role, capture instance name (defaults to schema_name), support net changes (bit, set it to 1 if you want both change data table-valued functions created), name of captured table's unique index, captured column list (null/default to all columns), filegroup for the change table (null/defaults to default filegroup)
  3. Query Change Data via 1 of 2 built in table-valued functions created during step #2
    1. For all changes (meaning a row is returned for each DML) use cdc.fn_cdc_get_all_changes_<capture_instance>
    2. For the net changes (meaning one row returned for each source row modified among 1 or more DMLs) use cdc.fn_cdc_get_net_changes_<capture_instance>
What are all of the CDC system objects available to me?
System Tables:
    • cdc.captured_columns
    • cdc.change_tables
    • cdc.ddl_history
    • cdc.index_columns
    • cdc.lsn_time_mapping
    • cdc.Schema_Name_CT (change tables) *this is just the default naming convention, configurable via the enable table sysproc
DMVs:
    • sys.dm_cdc_log_scan_sessions
    • sys.dm_repl_traninfo
    • sys.dm_cdc_errors

System Stored Procedures:

    • sys.sp_cdc_cleanup_change_table
    • sys.sp_cdc_disable_db_change_data_capture
    • sys.sp_cdc_disable_table_change_data_capture
    • sys.sp_cdc_enable_db_change_data_capture
    • sys.sp_cdc_enable_table_change_data_capture
    • sys.sp_cdc_get_ddl_history
    • sys.sp_cdc_get_captured_columns
    • sys.sp_cdc_help_change_data_capture

System Functions:

    • cdc.fn_cdc_get_all_changes_<capture_instance>
    • cdc.fn_cdc_get_net_changes_<capture_instance>
    • sys.fn_cdc_decrement_lsn
    • sys.fn_cdc_get_column_ordinal ( 'capture_instance' , 'column_name' )
    • sys.fn_cdc_get_max_lsn
    • sys.fn_cdc_get_min_lsn
    • sys.fn_cdc_has_column_changed
    • sys.fn_cdc_increment_lsn
    • sys.fn_cdc_is_bit_set
    • sys.fn_cdc_map_lsn_to_time
    • sys.fn_cdc_map_time_to_lsn
Do the change tables keep growing?
No, there is an automatic cleanup process that occurs every three days (and this is configurable). For more intense environments you can leverage the manual method using the system stored procedure: sys.sp_cdc_cleanup_change_table. When you execute this system procedure you specify the low LSN and any change records occuring before this point are removed and the start_lsn is set to the low LSN you specified.

How do you leverage CDC in SSIS Packages?

Books Online in CTP5 (November) actually has a sample package in the topic 'change data capture in integration services' and I found this to be a good starting point to build from. For my CDC/SSIS demo here is the Control/Data Flow I am using:
  1. Calculate Date Intervals (these will correspond to LSNs later) *also note that in both BOL and my own package we are using fixed intervals, in the real world this will be driven by a table solution which tells the SSIS package when the last successful execution occurs (starting point of next package iteration)
  2. Check is any data is available in the selected date/time interval. This is important because the rest of the package will fail if no data is ready. BOL recommends performing Thead.Sleep/WAITFORs here. I am not for demo purposes but its not a bad idea.
  3. Build the query via a SSIS variable *BOL states that SSIS packages cannot call the cdc.fn_cdc_getnet|all functions and must use a wrapper. Whether or not we end up being forced to do this, it is a good design practice, below is my custom function that SSIS calls passing in the start/end datetime values to get the actual change data in the data flow step below.
  4. Create a data flow task that executes the SSIS variable query (OLEDB source), and then splits the rows into via a conditional split based on the CDC_OPERATION column calculated in the function below.

CREATE function [dbo].[udf_Promotion] (
     @start_time datetime
    ,@end_time datetime
)
returns @Promotion table (
     SpecialOfferID int
    ,Description nvarchar(255)
    ,DiscountPct smallmoney
    ,[Type] nvarchar(50)
    ,Category nvarchar(50)
    ,StartDate datetime
    ,EndDate datetime
    ,MinQty int
    ,MaxQty int
    ,rowguid uniqueidentifier
    ,ModifiedDate datetime
    ,CDC_OPERATION varchar(1)
)
AS
BEGIN
 --declare local variables to hold LSNs
    DECLARE
  @from_lsn binary(10)
  ,@to_lsn binary(10)

 --Map the time interval to a change data capture query range.
    IF (@start_time IS NULL)
 BEGIN
        select @from_lsn = sys.fn_cdc_get_min_lsn('Sales_SpecialOffer')
    END
    ELSE
 BEGIN
  SELECT @from_lsn = sys.fn_cdc_map_time_to_lsn('smallest greater than or equal', @start_time)
    END
   
    IF (@end_time IS NULL)
    BEGIN
        SELECT @to_lsn = sys.fn_cdc_get_max_lsn()
    END
    ELSE
    BEGIN
       SELECT @to_lsn = sys.fn_cdc_map_time_to_lsn('largest less than or equal', @end_time)
 END
 
    --if same then exit
    IF (@from_lsn = sys.fn_cdc_increment_lsn(@to_lsn))
    BEGIN   
  RETURN
 END
 
    -- Query for change data
    INSERT INTO @Promotion
    SELECT
        SpecialOfferID,   
        Description,
        DiscountPct,
        [Type],
        Category,
        StartDate,
        EndDate,
        MinQty,
        MaxQty,
        rowguid,
        ModifiedDate,
        CASE __$operation
                WHEN 1 THEN 'D'
                WHEN 2 THEN 'I'
                WHEN 4 THEN 'U'
                ELSE NULL
         END AS CDC_OPERATION
    FROM
        cdc.fn_cdc_get_net_changes_Sales_SpecialOffer(@from_lsn, @to_lsn, 'all')

    RETURN
END

GO

OK, but what if I just want to load the actual columns that changed (ie for UPDATEs)?
I have not created a demo that does this yet but I can tell you that the key to enable this is the metadata column returned from the cdc.fn_get_net|all functions, __$update_mask. Here is Books Online description of this metadata column:
"A bit mask with a bit corresponding to each captured column identified for the capture instance. This value has all defined bits set to 1 when __$operation = 1 or 2. When __$operation = 3 or 4, only those bits corresponding to columns that changed are set to 1."
 
*__$operation = 3|4  are the pre and post update operations
 
Overall Impression?
I'm quite impressed with the new CDC feature built into the SQL Server relational engine. It is fairly easy to configure and use. In terms of enhancements, I think the matter of replacing the typical 'ETL Run' table should be considered. For example, when we configure this new technology going forward to replace our old source 'change identifier' columns we will still need a solution (usually table-based) for tracking when our ETL Packages have last ran (both successful and failed). It would be nice if we could somehow configure the CDC technology to say 'this SSIS Package is the only consuming application, therefore purge the data in a transactional manner once I retrieve it (which we could do manual right now I believe)'. Basically, give the option of replacing the LSN filtering of records to just retrieve and purge to so I can rely on the fact that the change table only contains data I have yet to process. Also, CDC can only work with SQL Server. While this is an obvious constraint, it would be nice to overcome it since SQL Server BI Systems will typically query other types of RDBMS for their source system data and not just SQL Server.
 
Overall the feature is great, it replaces the need for source column change identifers, and it relocates the ETL querying load to a seperate change table in the source system. If your organization has a complete SQL Server based environment, CDC is a great candidate for your future ETL solutions.

Print | posted on Monday, January 28, 2008 7:48 PM

Feedback

# re: SQL Server 2008: Change Data Capture (CDC)

Left by SQLDev at 10/13/2008 9:48 AM
How do we use CDC for related tables such as a master and detail where master having the PK and some basic details such as created by created on etc and the details having the entity specific attributes?
How do I use the CDC data for a single record modification by joining the master and details CDC tables?
Please help.

# re: SQL Server 2008: Change Data Capture (CDC)

Left by Derek Comingore at 10/13/2008 1:08 PM
Hi,

CDC is only available in SQL Server 2008 Enterprise, Developer ,and Evaluation editions. Furthermore, CDC is enabled at two levels, first a database level and then on specific tables you identify via the sys.sp_cdc_enable_table command.

sys.sp_cdc_enable_table
[ @source_schema = ] 'source_schema',
[ @source_name = ] 'source_name' ,
[ @role_name = ] 'role_name'
[,[ @capture_instance = ] 'capture_instance' ]
[,[ @supports_net_changes = ] supports_net_changes ]
[,[ @index_name = ] 'index_name' ]
[,[ @captured_column_list = ] 'captured_column_list' ]
[,[ @filegroup_name = ] 'filegroup_name' ]
[,[ @partition_switch = ] 'partition_switch' ]

If you have a Master|Child detail tables you would have to enable both tables for CDC if you need to detect and consume the change data of both.

# re: SQL Server 2008: Change Data Capture (CDC)

Left by Prasad at 10/14/2008 11:15 PM
I liked the explanation. Thanks for putting this togehter.

# re: SQL Server 2008: Change Data Capture (CDC)

Left by Automotive Software at 11/1/2008 10:19 AM
This is a great enhancement to SQL that was otherwise always difficult to do. We did it with SQL 2005 via CLR triggers and it worked pretty well.

# re: SQL Server 2008: Change Data Capture (CDC)

Left by m moen at 11/20/2008 6:49 AM
Derek,
This is a very thorough piece.
Thanks for putting this together.

# re: SQL Server 2008: Change Data Capture (CDC)

Left by yousef at 11/25/2008 6:55 PM
Can I capture changes occuring on data sources other than SQL database? for example, Oracle data source>?

# re: SQL Server 2008: Change Data Capture (CDC)

Left by Derek Comingore at 11/26/2008 8:44 PM
No, SQL Server 2008 CDC is a feature of the relational database engine. In order to support change data capture on our systems either the vendor would have to build that feature of MSFT COULD potentially create a RDBMS-neutral capturing process.

# re: SQL Server 2008: Change Data Capture (CDC)

Left by Durani at 2/26/2009 1:50 PM
No wonder CDC is very helpfull, but how to find who did the changes ? Is there any way to find that info?

# re: SQL Server 2008: Change Data Capture (CDC)

Left by Narasimha at 3/5/2009 2:42 AM
If i want to use the CDC+SSIS as alternative solution against Transactional Replication, How can i send the initial data in the table to the target? Not sure the transactional log contains the entries of that table right from the begining..

# re: SQL Server 2008: Change Data Capture (CDC)

Left by rahul aggarwal at 3/6/2009 7:19 AM
Hi,

How can I change the schema and user for CDC.
Because it creates its table in CDC schema. When ever I take the backup of this database. Backup doesn't include the schema, user and table that is created for the CDC, in the backup.
Is there any way that I can take the whole backup or i can change the schema name for CDC.

Thanks,

# re: SQL Server 2008: Change Data Capture (CDC)

Left by Kevin at 5/26/2009 2:43 PM
Since Yousef asked...

Attunity provides a plug-in for SSIS for CDC to:

Oracle, SQL Server 2000/2005, Mainframe and HP NonStop sources.

Sets up in minutes and is easy to use.

kevin.maguire@attunity.com

# re: SQL Server 2008: Change Data Capture (CDC)

Left by T at 6/8/2009 4:08 PM
Personally, I think CDC is a pile of crap. I have been trying to use it to track specific field changes on tables by placing a trigger under the CDC table. It runs for a while but then fails without telling which table it failed to load data into. My trigger may be in error but I am not sure which trigger failed. By looking at [dm_cdc_errors] how do you know what table it failed on?

Your comment:





 
Please add 3 and 7 and type the answer here:

Copyright © Derek Comingore

Design by Bartosz Brzezinski

Design by Phil Haack Based On A Design By Bartosz Brzezinski