I pulled in the scripts and hit an error on the disable cdc call from the scripts document referenced at the bottom of the article.
@source_schema = 'dbo'
, @source_name = 'Employee'
, @capture_instance = 'dbo_Employee'
, @supports_net_changes = 1
Throws an error:
[color=#FF0000]Msg 8144, Level 16, State 2, Procedure sp_cdc_disable_table, Line 0
Procedure or function sp_cdc_disable_table has too many arguments specified.[/color]
Books online specifies the syntax as:
[ @source_schema = ] 'source_schema' ,
[ @source_name = ] 'source_name'
[ , [ @capture_instance = ] 'capture_instance' | 'all' ]
So if you get rid of the support_net_changes it runs ok.
Besides auditing, another use of CDC is for data warehouseing and reporting. No need to write specialized code to pull in the changed records, you have a nice method of handling that using CDC without relying on the MERGE functionality in 2008 or Slowly Changing Dimensions tasks in SSIS which can be a performance hinderance on large data sets.