Multiple distribution databases?

  • In my development environment I need to maintain more than one set of transactionally-replicated databases. Publishers, distributor, and subscribers are all on a single SS2K server. I know that I can specify multiple distribution databases for the distributor, but cannot determine if it is possible to configure each publisher/subscriber pair to use a separate, individual distribution database.

    I'd like to isolate problems in one publisher-distributor-subscriber from any others on the server. Is there a way?

    Thanks for your help,

    Steve Armistead,

    Database Administration

    Panther Systems Northwest, Inc.

    Vancouver, WA

    Steve

  • Sorry, no go. Only one distributor database per publisher. Try using profiler to monitor the transactions for a specific spid or database but I haven't tried and don't have in front of me.

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

    Edited by - antares686 on 07/25/2002 6:32:18 PM

  • Agree with Antares. What kind of problems are you having?

    Andy

    http://qa.sqlservercentral.com/columnists/awarren/

  • I'm not having any particular problem, yet. I say "yet" because I forsee the potential for problems if I need to restore a publisher & subscriber. It's my understanding that the distribution database is a main participant in the replication, meaning it should be backed up with the publisher/subscriber, and restored when needed. If the distributor is supporting multiple publishers, restoring it to a previous state will impact all of the publishers, right?

    So, I'm trying to understand how to use multiple distribution databases, one for each publishing database on the server. BOL hints at this in their Replication FAQ (When do I need multiple distribution databases?), and EM allows me to create multiple distribution databases in the "Configure Publishing, Subscribers, and Distribution..." selection from the replication menu. I cannot determine how to specify a particular distribution database for a publishing database, though. There may not be a way, but if that's the case then why have the ability to utilize multiple databases on the distributor?

    Thanks for your opinions and findings,

    Steve Armistead,

    Database Administration

    Panther Systems Northwest, Inc.

    Vancouver, WA

    Steve

  • My recovery plan is to just snapshot everything and move on. Doesnt seem like its worth trying to salvage. Of course I have the luxury of a 100m switched network, only 40g or so data spread across a few db's, and the time to let it happen.

    You can have multiple distribution databases on a server, but they serve different publishers. I'll admit to not exploring this enough, I'd be interested to hear from anyone who does put dist db's on separate box.

    Andy

    http://qa.sqlservercentral.com/columnists/awarren/

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply