Change Data Capture feature of SQL 2008 is based on Transactional Replication. CDC and Transactional Replication used the same internal stored procedure sp_replcmds to retrieve data updates from the transaction log. However, unlike Transactional Replication, CDC does NOT require the tables to have a unique index (or Primary Key). In fact CDC can be use
Read More »
content provided by: Akbar Farishta, Technical Lead, Microsoft SQL Server Support I wanted to post an update to Snapshot Agent Performance –MaxBCPThreads blog posting. We recently encounter a performance problem trying to push a 120gig snapshot down to a subscriber. The Distribution Agent was taking a long time doing a Bulk Insert on an 80gig
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 »
The Microsoft SQL Server Support team uses various scripts to collect Replication and Performance data from customer’s SQL Servers. These scripts extract data into either text files or into temporary databases which are then backed up and sent to Microsoft SQL Engineer for analysis. Below are links to some of these common data collection scripts.
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 »