Chris,

Some great info there, thank you. The 20k deletes was just to remove the test data, its not something that would occur regularly in the live environment. The normal workload is a steady stream of inserts and a small amount of updates. Deletes will be rare.

Peer-to-peer sounds like it would be the best fit for what I need but unfortunately I'm stuck with 2005 Standard for this project. The basic requirement is to have a secondary copy of the database that is in a ready state so that the application stays up if the WAN link fails over to the DR site.

If I create the FK constraints with NOT FOR REPLICATION, should I create them manually at the subscriber? Or does that defeat the purpose?