Home Dashboard Directory Help
Search

Is there bug with cdc.fn_cdc_get_net_changes_.... in SQL Server 2012 by VenSree


Status: 

Active


2
0
Sign in
to vote
Type: Bug
ID: 782085
Opened: 3/25/2013 4:24:20 PM
Access Restriction: Public
0
Workaround(s)
view
3
User(s) can reproduce this bug

Description

Below script to bring net changes from cdc enabled table for given dates. This always fails on the second table.

DECLARE @begin_time datetime, @end_time datetime, @begin_lsn binary(10), @end_lsn binary(10);

select @begin_time = min(tran_begin_time) from [cdc].[lsn_time_mapping];
Select @end_time = max(tran_begin_time) from [cdc].[lsn_time_mapping];

SELECT @begin_lsn = sys.fn_cdc_map_time_to_lsn('smallest greater than', @begin_time);
SELECT @end_lsn = sys.fn_cdc_map_time_to_lsn('largest less than or equal', @end_time);

SELECT * FROM cdc.fn_cdc_get_net_changes_CustomerChanges(@begin_lsn, @end_lsn, 'all')

SELECT * FROM cdc.fn_cdc_get_net_changes_ProductChanges(@begin_lsn, @end_lsn, 'all');
Details
Sign in to post a comment.
Posted by Microsoft on 4/8/2013 at 1:33 PM
Hi VenSree,

given the load here and the backlog of MS Connect items we are working on it will take us some time to get back to you. If this is related to an urgent issue in production I recommend you contact our Support engineers. You may already have a local support representative. If not you'll find more information on http://www.microsoft.com/microsoftservices/en/us/support.aspx.
Anyways, we will get back to you on this one.

Best regards
Jean-Yves Devant
Program Manager Servicing and Lifecycle Experience of High Availability Technologies in SQL Server
Posted by VenSree on 4/3/2013 at 10:08 PM
Hello Jean-Yves
Any update on this please?
Posted by Microsoft on 3/29/2013 at 11:16 AM
Hi VenSree,
    
thanks for taking the time to share your feedback, this is really important to us.
We will investigate the issue and get back to you.

Best regards
Jean-Yves Devant 

Program Manager Servicing and Lifecycle Experience of High Availability Technologies in SQL Server
Sign in to post a workaround.