Q:

Change Data Capture - Microsoft Best Practice for capturing data changes?

We have some debate on our development team regarding the best way to capture changes in data in some of our tables. I am very impressed with Change Data Capture and believe it is the best way to capture this sort of data, and that this is what Microsoft designed CDC to do.
For those of you who've had to deal with this sort of thing, have you found CDC to be the Microsoft best practice way of capturing data changes in tables?
Thanks very much.

A:

It's absolutely the easiest and most efficient; if the alternative is to create triggers and write to audit tables, I'd take CDC any day. It works very well and requires little setup. 
Whether it would be the best for your scenario, that would require a little more info. 

