Below are cause and recommendation for the SQL Replication LogReader error “The specified LSN (…) for repldone log scan occurs before the current start of replication in the log (…).’. When the LogReader starts, it verifies the Last Distributed transaction (last transaction in msrepl_transactions) still exists in the transaction log. This confirms the Published database
Read More »
Content provided with help of Jonathan Clark, Microsoft SQL Server Escalation Services Oracle to SQL Server replication is used to support customers migrating Oracle legacy application to Microsoft SQL Server. The data changes in Oracle can be replicated near real-time to a SQL Server database. Here is a little background information on the Oracle to
Read More »
I meet with a customer today planning for Peer-2-Peer Replication in conjunction with Microsoft Amalga, our Hospital Information System solution. I thought others would benefit from some of the Q&A that were raised in this meeting. I hope you too find these helpful in your projects. 1. How to monitor replication? >>>Tracer Tokens can be
Read More »
When Replication the EXECUTION of a stored procedure to a subscriber select the “serialized transaction” and and wrap the SP execution within a transactions. This ensures the changes are replicated as a single stored procedure execution and not as individual row-level updates. See: Publishing Stored Procedure Execution in Transactional Replication “The serializable option is recommended
Read More »
José Moreira Neto Microsoft Escalation Engineer I ran into an issue where the customer was complaining that Merge Replication was generating “fake” conflicts. This customer has a straight SQL Server Merge Replication with no filters where the only non-default setting is the use of the Microsoft Maximum Conflict Resolver a very specialized feature in Merge
Read More »