• start_lsn tran_begin_time tran_end_time tran_id tran_begin_lsn
  • 0x00000153000001900001 2012-09-02 04:28:05.620 2012-09-02 04:28:05.620 0x00 0x00000000000000000000
  • 0x00000153000001CD0001 2012-09-02 04:33:06.450 2012-09-02 04:33:06.450 0x00 0x00000000000000000000
  • 0x000001530000020A0001 2012-09-02 04:38:07.273 2012-09-02 04:38:07.273 0x00 0x00000000000000000000
  • 0x00000153000002470001 2012-09-02 04:43:08.157 2012-09-02 04:43:08.157 0x00 0x00000000000000000000


As you can see I get tran_id = 0X00 and trans_begin_lsn is also zero.

As soon as I get this my ssis package can no longer process be cause the start_LSN is so big in my cdc_state table that my ssis package can never find the LSN in my CT that is way smaller than this LSN.

When I try to reset the cdc instance. The type of record get added into the LSN_Time_Mapping table.

The only fix I did was to drop the cdc instance and do a full recreation.

I am worry that this will happen again in my new cdc instance in the future.

As anyone have the fix or anything to prevent this from happening.