Using Sql Server Change Data Capture with a frequently changing schema
Posted
by
Pete
on Programmers
See other posts from Programmers
or by Pete
Published on 2013-06-18T10:04:30Z
Indexed on
2013/06/25
16:28 UTC
Read the original article
Hit count: 320
sql-server
|migration
We are looking into enabling Sql Server Change Data Capture for a new subsystem we are building.
It's not really because we need it, but we are being pushed for having a complete history traceability, and CDC would nicely solve this requirement with minimum effort on our parts.
We are following an agile development process, which in this case means that we frequently make changes to the database schema, e.g. adding new columns, moving data to other columns, etc.
We did a small test where we created a table, enabled CDC for that table, and then added a new column to the table. Changes to the new column is not registered in the CDC table.
Is there a mechanism to update the CDC table to the new schema, and are there any best practices to how you deal with captured data when migrating the database schema?
© Programmers or respective owner