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 »
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 »
Have you seen errors like these below when attempting to run SQL Replication Wizard or start a SQL Agent job? TITLE: Microsoft SQL Server Management Studio —————————— SQLServerAgent is not currently running so it cannot be notified of this action. (Microsoft SQL Server, Error: 22022) SQL Server blocked access to procedure ‘dbo.sp_get_sqlagent_properties’ of component ‘Agent
Read More »
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 »
We noticed a large published database was taking a long time for the Snapshot to be applied to the subscriber. Looking further in sp_who and sys.sysprocesses we noticed only one Distribution Agent thread executing the bulk insert statements. It took a while but we discovered the publication was created using “concurrent snapshot” option. -MaxBcpThreads number_of_threads
Read More »