Understanding the CDC State Value

Bradley Schacht

Bradley Schacht is a Cloud Solution Architect on the state and local government team with Microsoft based in Jacksonville, FL. He has co-authored 3 SQL Server books including "SQL Server 2014 Professional Administration". As a former consultant and trainer, he uses his experience on many parts of the Microsoft BI and data platform to help customers deliver the best possible solutions. Bradley frequently presents at community events around the country. He is a contributor to sites such as SQLServerCentral.com and an active member of the Jacksonville SQL Server User Group (JSSUG).

You may also like...

4 Responses

  1. I had to the same effect and am glad you explained why. Just did the original demo on SQLLucnh.com on Tuesday with Patrick.

    • It completely confused me why it was happening until I did some more research. I’ll have to go check out the recording from SQL Lunch sometime this week. The 2012 CDC stuff is exciting.

  2. Jonathan H says:

    Thank you so much for this. I was banging my head against the wall trying to figure out why the first incremental load never seemed to pick up changes. I’m giving a demo of CDC to my team soon, and didn’t want to run the incremental package twice, “just because”. Now I can explain why I put Mark CDC start in the initial load package for the demo, and why I probably wouldn’t do so for a real package.

  3. You say “ILUPDATE – Initial Load Update – Results from choosing the operation Get Processing Range in the CDC Control task while the first run of an update package while the initial load is still in process.”

    While which?

Leave a Reply