Share this PostContent 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
Read More »
Share this PostWhen 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
Read More »
Share this PostFor SQL 2005 and SQL 2008 the sp_removedbreplication stored procedure works great for removing the SQL Replication bits from a database. SQL 2000 has an older version of this SP which doesn’t always cleanup the database. You can use the following steps in SQL 2000 to remove the leftover Replication bits. Problem Description
Read More »
Share this PostLatency problems are often caused when series of transactions are trying to move a large batch of commands from the Publisher to the Distributor to the Subscribers. The queries below show overall rows counts and index statistics for commands stored in the Distribution database. Use the results of these queries to look for
Read More »
Share this PostQuestion to research: How can subscribers with just VBA do an “on demand synchronization”? Background: SQL 2008 R2 Standard Edition Publisher/Distributor with SQL 2008 R2 Express subscribers. SQL Express does not include SQL Agent to schedule Replication jobs, therefore, the subscribers are setup using “push” Replication from the Publisher. They would like the
Read More »