Transfer or script-out cdc enabled tables using SMO - by D. S. Dodiya

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 774042 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 12/11/2012 9:42:54 AM
Access Restriction Public

Description

I have some tables with CDC enabled in source server and need to transfer those tables to target server with CDC enabled. But SMO is not supporting to script-out CDC enabled tables.
Sign in to post a comment.
Posted by Alex [MSFT] on 1/31/2013 at 3:15 PM
Hello

We took a look at this DCR (this is not defect but actually DCR to add suport of SMO to CDC) along with several others. Unfortunately based on current customers votes count we decided not to proceed with this DCR in the next release. However, we have taken note of this internally, and when we revisit this functionality in the future, we will try and get this implemented.

Thanks for writing to Microsoft.
Alex Grach (MSFT)
Posted by D. S. Dodiya on 12/12/2012 at 2:26 PM
I am using SQL Server Management Objects (SMO) - > Transfer class in order to transfer objects from one SQL Server (Source Server) to other SQL Server (Destination Server). Actually there are some tables with CDC enabled in source server and need to transfer those tables to target server with CDC setting. So we need not to enable CDC for those tables on destination server manually.

Posted by Sethu [MSFT] on 12/11/2012 at 3:48 PM
Thanks for reporting this issue. Could you please attach the T-SQL script that you used to enable CDC on table and list of steps you performed to generate scripts? ( Was it done using SMO object model / through Generate Scripts Wizard )

Thanks
Sethu Srinivasan [MSFT]
SQL Server