The Working of Microsoft SQL Server CDC

Modern-day businesses have to preserve historical data and take measures to prevent data breaches. In this regard, Microsoft took the lead in 2005 when it launched the SQL Server CDC.

The 2005 version of SQL Server CDC had certain flaws which were ironed out in an updated release in 2008. Some of the functionalities included tracking and capturing all changes that take place in the SQL Server database tables without taking the help of additional programs and applications. Till 2016, SQL Server CDC was offered by Microsoft in its high-end Enterprise editions but later was available in the Standard version too.

SQL Server CDC captures and records all activities like Insert, Update, and Delete applied to a SQL Server. Column information and metadata required for posting changes to the target database are recorded in modified rows that are then stored in change tables representing the architecture of the columns in the tracked source tables. SQL Server CDC also tracks all changes recorded in the mirrored tables.

There are additional columns tracking changes at the source tables and the data present is in the following format.

· __$start_lsn and __$end_lsn that show the commit log sequence number (LSN) assigned by the SQL Server Engine to the recorded change

· __$seqval that shows the order of that change related to other changes in the same transaction, __$operation that shows the operation type of the change, where 1 = delete, 2 = insert, 3 = update (before change), and 4 = update (after change)

· __$update_mask that is a bitmask defined for each captured column, identifying updating columns

SQL Server CDC is an excellent method to preserve historical data.

Comments

The Change Data Capture (CDC) Feature in Microsoft SQL Server

Several issues are faced by organizations today in the areas of data security and safety and ramping up systems for preservation of historical data. Leading database platforms took steps in this regard by launching data audits, timestamps, complex queries, and triggers, one of them being Microsoft. It led the innovation when in 2005, it introduced the SQL Server CDC with the “after date”, “after delete”, and “after insert” features. SQL Server CDC captures and records all activities like insert, update, or delete that are applied to a SQL Server table. Changes made are available in a user-friendly relational format and metadata and information that are required for posting changes to the target databases are captured in modified rows. These are stored in change tables with the same structure as the columns in the tracked source tables. SQL Server CDC also tracks and records changes in the mirrored tables with column structures that are the same as the source ...

The Evolution of Technology of Oracle Change Data Capture

Oracle change data capture ( CDC) was first launched with the 9i version as an in-built tool of the Oracle database. It was a tool that recorded and monitored all changes made in the user tables in a database. These changes were then stored in change tables and used in ETL applications for later processing and transferring to other data warehouses and databases. The release version of Oracle change data capture had triggers placed in the source database. However, database administrators found this technology very invasive and did not favor it. Ultimately, Oracle changed the Oracle change data capture technology and released it with the 10g version after naming it Oracle Streams. The working of this release was different. Oracle change data capture used the redo logs of the source database along with a replication tool of Oracle Streams. This technology turned out to be very successful and a highly optimized method to identify and move change data to a target ...

ALL DATA SOLUTIONS

Search This Blog