Source tables change over time. A data mart or data warehouse that is based on those tables needs to reflect these changes. However, a process that periodically copies a snapshot of the entire source consumes too much time and resources. Alternate approaches that include timestamp columns, triggers, or complex queries often hurt performance and increase complexity. What is needed is a reliable stream of change data that is structured so that it can easily be applied by consumers to target representations of the data. Change data capture in SQL Server provides this solution.
The change data capture feature of the Database Engine captures insert, update, and delete activity applied to SQL Server tables, and makes the details of the changes available in an easily-consumed, relational format. The change tables used by change data capture contain columns that mirror the column structure of the tracked source tables, along with the metadata needed to understand the changes that have occurred on a row by row basis.
Source:
http://msdn.microsoft.com/en-us/library/bb895315.aspx
http://www.mattmasson.com/index.php/2011/12/cdc-in-ssis-for-sql-server-2012-2/
Best Regards,
Ravindra
The change data capture feature of the Database Engine captures insert, update, and delete activity applied to SQL Server tables, and makes the details of the changes available in an easily-consumed, relational format. The change tables used by change data capture contain columns that mirror the column structure of the tracked source tables, along with the metadata needed to understand the changes that have occurred on a row by row basis.
Source:
http://msdn.microsoft.com/en-us/library/bb895315.aspx
http://www.mattmasson.com/index.php/2011/12/cdc-in-ssis-for-sql-server-2012-2/
MSBI (SSIS/SSRS/SSAS) Online Training:
Best Regards,
Ravindra
No comments:
Post a Comment