I think distribution database keeps track of transactions that are processed by distribution agent. So, as you suggest, the distribution agent will queue up all the trasactions and then...

You can also accomplish this from Query Analyser with something like:

use master

GO



exec sp_adddistributor  @distributor = @@servername, @password = N'your_password'

GO



- Adding the distribution database

exec sp_adddistributiondb...

I have three servers at this point (a publisher and two subscribers), but I need to be able to support more subscribers in the future.

Dan, I could still use something...

That's why your range is huge - to avoid having subscribers step on each others' toes... or how do you assign a new (maybe non-consecutive) range to a subscriber that...

Yeah, it makes sense what you are doing here... I'm guessing you still have the 'Auto Range Management' option on for these tables (with range size of 1000000 or...

quote:

---

I now reset all tables' IDs after each replication using some simple SQL and a subscribers table which contains a subscriber number...