This problem was brought to our attention recently by one of our customers. CDC LogScan job fails, possible Error Message: Log Scan process failed in processing log records. Operand type clash: int is incompatible with uniqueidentifier Operand type clash: int is incompatible with datetime The Log-Scan Process failed to construct a replicated command from log
Read More »
By Sateesh Yele, Microsoft SQL Escalation Services This DMV sys.dm_cdc_log_scan_sessions is very useful in determining the latency with Change Data Capture (CDC). I inserted one record in the database and started the CDC capture job after around 2 minutes. It showed the latency as 165 seconds. It is difference in seconds, between end_time and last_commit_cdc_time
Read More »
–by Liwei Yin, Microsoft SQL China Support Assume you have CDC enabled for a table with text/ntext column. 1 You moidfy the colum type from text/ntext to varchar(max)/nvarchar(max) 2 Then you do an update to the column thereon, tried to assign a large size (more than 8000)value to the column, the CDC may fail and
Read More »
While troubleshooting a customers environment I encountered the following 9003 Exception error message captured in SQL Server Profiler. “The log scan number (42:358:1) passed to log scan in database ‘<db name>’ is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this
Read More »
Replicate Execution of Stored Procedure and CDC: With Transactional Replication you can replicatethe execution of the Stored Procedure like this: This has several advantages as discussed in this article: http://msdn.microsoft.com/en-us/library/ms152754.aspx . When you enable Change Data Capture (CDC) at the Database level, replication of the stored procedure execution will NOT work. This is By Design.
Read More »