SQL Server 2005 Transactional Replication causing deadlocks

[SQLWilts]

Hi,

We have been running SQL Server 2005 since the RCM in November. All seems to be going well with it (except the SSMS seems slower than EM in general) with the exception of replication.

For some reason transactional replication is causing deadlocks on the publication, and I cannot for the life of me see why. The snapshot agent was run once, and does not run again unless I tell it to. I thought that replication just worked with the logs (a form of automated log shipping). Am I right?

We are using SQL 2005 Enterprise Edition on a dual processor machine.

STOP PRESS! Just found that the snapshot agent runs periodically! Anyone any ideas as to why this would do this and how to stop it?

 

[philhege]

What's in the schedule for the agent?

Phil Hegedusich
Senior Programmer/Analyst
IIMAK

http://www.iimak.com

-----------
Eschewing obfuscation diurnally.

 

[SQLWilts]

Hi Philhege,

It was running once an hour. I don't even know why, in transactional replication, it should run on a schedule at all. Surely it should only run as and when I call it manually - as in to re-initialise a subscriber.

Anyway, I have changed it to run once a day at 01:00 on one publication and 02:00 on another. Any ideas as to the implications of this?