Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When setting up a new subscription to a publication (transactional replication) from 64-bit SQL Server 2005 to 64-bit SQL Server 2005 the Snapshot Agent on the publisher consumes 100% of the CPU. I am using SSMS to create the new subscription. My initial impression is that this could be from row locking occurring during the generation of the snapshot but I have read that a concurrent snapshot is generated by default in SQL Server 2005, and that row locking shouldn't be a concern.

As this is a production server I would like to be able to initialize replication without bringing the box to it's knees. Any suggestions would be helpful and appreciated.

share|improve this question
What process (according to task manager) is spinning the CPU? If the SQL Server then what does it show is going nuts? – mrdenny Oct 22 '09 at 20:41

is the distribution database running on the production db?
If you want to minimizse the load on your production db, setup the distribution db to run at the subscriber, not the publisher.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.