Tag Info

Well indeed, if the log is removed - blown away by the restore, and the changes were not yet applied then those changes are permanently lost. The core data is still out there though right? So you could consider a full load for suspect tables. What is known about there changes suspect to be missing? Can they be identified through some flag column or date ...

While it is not possible with SQLserver CDC directly, there are commercial tools out there which can readily perform this task. I work for Attunity, which has a full featured 'Replicate' product. Define a source DB; define a target; include or exclude desired tables (wildcards); optionally define some per-table or global transformations; and 'click' to ...

No, it will only work within the same database. After all, what do you expect to happen if the second database goes offline, gets dropped, becomes corrupt, has permissions changes, etc.? Now, once the CDC tables are created, I guess one potential workaround would be to place INSTEAD OF INSERT triggers on them, and divert the data to identical tables in ...