A SQL Server Management Studio add-in to source control your database in Subversion or Team Foundation Server.
Is there a recommended practice for handling SQL Server CDC objects when using Source Control?
Source control tracks the user, schema, role, and table valued functions created, but does not seem to track the cdc System Tables.
Is it best to just leave CDC objects and configuration out of Source Control? Or implement them only via migration scripts?
Any advice or first-hand experience is much appreciated!
- Posts: 1
- Joined: Fri Jun 07, 2013 5:39 pm
I'm not sure as to a "recommended" method- but it's correct that we don't track "system" level objects (this is a limitation of the SQL Compare engine which Source Control uses behind the scenes).
I guess manipulating these objects behind the scenes may well work, although it's not something I've tried personally...
- Posts: 1120
- Joined: Wed Jun 16, 2010 11:10 am
- Location: Red Gate
Return to SQL Source Control 3
Who is online
Users browsing this forum: Yahoo [Bot] and 0 guests