Share this PostYes, post mostly Replication or High Availability topics, but I found this interesting enough to share on my ReplTalk blog. These are the troubleshooting and resolution we used to help a customer explore faster ways to update a 100 million row table. Problem Description Customer was running UPDATE query affecting 100 million rows.
Read More »
Share this PostIs your transaction log over 5gb? Have you checked to see how many Virtual Log Files (VLFs) exists in your transaction logs? If not, I would suggest you add to your many list of high priority tasks checks to see how many VLFs exists for your transaction logs. A large number of VLFs
Read More »
Share this Postreposting from Claudia Silva Microsoft SQL Escalation Services United Kingdom http://blogs.technet.com/b/claudia_silva/ Problem: The upload message to be sent to Publisher ‘XXX’ is being generated The merge process is using Exchange ID ‘XXXXX’ for this web synchronization session. No data needed to be merged. Request message generated, now making it ready for upload. Upload
Read More »
Share this PostWorking with a customer to setup a large subscriber we noticed the Merge Agent was NOT doing a BULK INSERT, but instead was doing row-by-row insert. This had significant overhead for the Merge Agent resulting in longer then expected initial/reinit synchronization times. Downloaded 33 change(s) in 'Customer' (33 inserts): 33 total Applied the
Read More »
Share this PostHere is a great posting by Kevin Locke on a problem he encountered when data modifications occurred near the top of a complicated replication filter configuration. These changes can cause “partition change” which triggers re-evaluation of all child data; also known as “repartitioning”. Kevin’s solution was to add an index to the Merge
Read More »