Share this PostSymptom Creating a Peer 2 Peer publication from SQL scripts and you observe the Distribution Agents failing with “incorrect syntax near”. These messages can be observed in SQL Server Agent job history, in SQL Profiler Trace, or in Agent -Output logging. Errors show below were raised on (insert) stored procedure for Production.Product table
Read More »
Share this PostBy default Replication is configured to purge historical data older then 48 hours. For troubleshooting, its nice to pause or postpone purging of replication agent historical data. To change the History Cleanup settings use SQL Server Management Studio, alt-click “Replication” folder and select “Distributor Properties”. Share this Post
Share this PostChris SkorlinskiMicrosoft SQL Escalation Services I wanted to share this problem which started down a “your data is wrong” path, but ended up with “your customer scripts to create Transactional Replication need to be tweaked”. Customer reported the following error in Replication Monitor: Cannot update identity column ‘OrderID’. Looks like Distribution Agent is
Read More »
Share this PostChris SkorlinskiMicrosoft SQL Server Escalation Services While working with a customer on a Merge Replication project, we encounter a potential road block. They had a published table which exceeded the number of columns allowed for Merge Replication. From this article https://technet.microsoft.com/en-us/library/ms151749(v=sql.105).aspx: If your application does not require column-level tracking, it is recommended that
Read More »
Share this PostThis 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
Read More »