Comment Feed for Channel 9 - CDC - Change Data Capture SQL Server 2008 http://ecn.channel9.msdn.com/o9/previewImages/100/259892_100x75.jpg Channel 9 - CDC - Change Data Capture SQL Server 2008 CDC or Change data capture is a new feature in SQL Server 2008, which is an ability to record changes to table data into another table without writing triggers or some other mechanism, Change data capture records the changes like insert, update, and delete to a table in SQL server thus making the details of the changes available in relational format.Find more information on the Topic http://www.microsoft.com/sql/2008/prodinfo/download.mspx https://connect.microsoft.com/SQLServer/content/content.aspx?ContentID=5507 http://blogs.msdn.com/usisvdehttp://blogs.msdn.com/ajaiman en Wed, 22 May 2013 01:46:50 GMT Wed, 22 May 2013 01:46:50 GMT Rev9 Re: CDC - Change Data Capture SQL Server 2008 Myonly concern were what happened with distributed transaction

Also Does any body knows any such feature in Oracle?

posted by kamii47

]]> http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c633347783670000000 Tue, 01 Jan 2008 09:59:27 GMT http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c633347783670000000 kamii47 Re: CDC - Change Data Capture SQL Server 2008 My concern is about the security trace: is it possibile to trace the current user application name ?
Normally we connect application to SQL using a unique trusted connection (windows authentication), but we are interested to log all db changes along with the current logged (application) user; otherwise we know the db changes but not who made them.

posted by MaurizioR

]]> http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c633350588830000000 Fri, 04 Jan 2008 15:54:43 GMT http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c633350588830000000 MaurizioR Re: CDC - Change Data Capture SQL Server 2008
MaurizioR wrote:
Yes, it is an exiciting feature.
My concern is about the security trace: is it possibile to trace the current user application name ?

Normally we connect application to SQL using a unique trusted connection (windows authentication), but we are interested to log all db changes along with the current logged (application) user; otherwise we know the db changes but not who made them.


With triggers we would do this by getting the user_name from sql and we could insert it into the audit tables. This works well as long as you have a two tier application with each user having thier own connection.

With 3-Tier or web apps you are unable to use the user_name since you are probably using a single user id or connection pooling. So, what we would do is add a field or fields to each table that the application would populate on each insert/update. This way the audit data could capture who made the change. For delete I guess you would have to get creative like not allowing record deletes and just setting a delete flag... or you could update the record with all blank/null values prior to deleting it.

I would assume that you could do a similar thing with CDC?

BOb

posted by pilotbob

]]> http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c633350999630000000 Sat, 05 Jan 2008 03:19:23 GMT http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c633350999630000000 pilotbob Re: CDC - Change Data Capture SQL Server 2008 We already implement a similar mechanism inside our product: for each table, dedicated fields are in charge to store the InserUserName and LastUpdatedUser. We can extend them, adding the DeletedUserName column.

Anyway it is not acceptable to implement a logical delete for us, while it is possible to think to a solution that updates the DeletedUserName before physically deleting the record.

Alternatively, an elegant solution could be:
SQL Server stores a dedicated variable inside the CDC table, i.e. CDCUserName.
By default, CDCUserName contains the connection user name (SQL auth or Win auth), so the console changes are logged too.

At runtime, the application should be able to assign CDCUserName with the current application user for that specific session only. The mechanism should be compatible with connection pooling.

Regards,

Maurizio

posted by MaurizioR

]]> http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c633353032430000000 Mon, 07 Jan 2008 11:47:23 GMT http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c633353032430000000 MaurizioR Re: CDC - Change Data Capture SQL Server 2008 http://www.codeplex.com/CDCHelper

posted by ignatandrei

]]> http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c633536081290000000 Wed, 06 Aug 2008 08:28:49 GMT http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c633536081290000000 ignatandrei Re: CDC - Change Data Capture SQL Server 2008 How do I retrieve the CDC data for a single record modification by joining the master and details CDC tables?
Please suggest.

posted by SQLDev

]]> http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c633595065720000000 Mon, 13 Oct 2008 14:56:12 GMT http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c633595065720000000 SQLDev Re: CDC - Change Data Capture SQL Server 2008 oracle "change data capture" for auditing.  http://www.wisdomforce.com/products-DatabaseSync.html
It is a log base CDC replication

posted by DBAJohn

]]> http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c633640124310000000 Thu, 04 Dec 2008 18:33:51 GMT http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c633640124310000000 DBAJohn Re: CDC - Change Data Capture SQL Server 2008 Virtually every project that I've worked on has required full audit tracking as most of them are ecommerce or financial projects.  Using an IsDeleted flag is the easiest and overall best way to go.  Adding the field to an existing site and fully implementing it should take no more than a couple days.  If it takes longer than that, you are doing something wrong.  For tables that allow changes, we add the following fields at the end of the table:

[LastChangeBy] uniqueidentifier
[LastChangeDate] datetime
[IsDeleted] bit

For tables that do not allow changes (i.e. Payments), we add the following fields at the end of the table:

[CreatedBy] uniqueidentifier
[CreatedDate] datetime

This way we always know exactly who made what change, and when.

posted by mercsd

]]> http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c633812156340000000 Sun, 21 Jun 2009 21:13:54 GMT http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c633812156340000000 mercsd Re: CDC - Change Data Capture SQL Server 2008 Hi,

It would be nice to know how you would apply this to a real world scenario. Is this used only for auditing? 

If every change is captured, and updates are captured twice, it may lead to huge change tables over a relatively short time. 

 

Karim

posted by klameer

]]> http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c634132308240000000 Sun, 27 Jun 2010 10:20:24 GMT http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c634132308240000000 klameer Re: CDC - Change Data Capture SQL Server 2008 i need to show only the updated columns
when user selects the date periods and the person name - i need to display any updated info about that person during that period.
 
thanks
 

posted by justin

]]> http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c634237220570000000 Tue, 26 Oct 2010 20:34:17 GMT http://channel9.msdn.com/Blogs/ashishjaiman/CDC-Change-Data-Capture-SQL-Server-2008#c634237220570000000 justin