new application needs to be ready for replication

[jmille34]

Sorry if this isn't the best place for this. I don't see an sql server database design topic.

We are starting version 2 of our flagship product, and it needs to be ready for replication between servers across the internet. We use SQL server 2000 up to this point, and the replication has been wonky at best, mainly due to using identity fields for the primary key on most tables, and merge replication gets screwy when you do that.

Can anyone point me to a best practices article that refers specifically to MS replication strategies? I'd like to get this started on the right foot, and I want a list of things not to do, as opposed to finding out 6 months later like we usually do.

 

[ZenRaven]

I think this post would be more appropriate in the Setup and Administration forum but here's what I've got anyway.

Microsoft is pretty good at putting out Best Practices documentation on most of it's products. For SQL Server, these are almost always found in BOL. Here's the MSDN link Best Practices for Replication Administration