Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

More than 1 Distributor database per instance? Expand / Collapse
Author
Message
Posted Wednesday, January 08, 2014 9:55 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: 2 days ago @ 12:57 PM
Points: 461, Visits: 1,265
I've read that you can only have 1 distribution database per instance. The problem I am running into with that design is that now my point of failure rests on the Distributor, and since you cannot mirror the distribution database - I am left with little else than some form of clustering. The issues in my environment are mostly network related concerns, so justifying an MSCS cluster (or some other 3rd party configuration) is not easily sold.

Is there any possibility to get 2 or more Distributors (distribution databases) to work in the same instance? Or is this just the way it is?

Many thanks in advance for any and all help on this...
Post #1528966
Posted Wednesday, January 08, 2014 10:40 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 11:52 AM
Points: 41,530, Visits: 34,446
You can only have one distribution database per instance.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1528993
Posted Wednesday, January 08, 2014 11:33 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: 2 days ago @ 12:57 PM
Points: 461, Visits: 1,265
Hi Gail - thank you for the confirmation on this (I was the bad guy for a while due to this news to my management team), but do you have a recommendation for some form of redundancy for the distribution database other than Clustering? The only other thing I have thought of is to spin up yet another mirrored pair that get replicated to themselves from the main mirrored pair, but that is still going to require a distribution server for their replication (to keep the secondary one in sync).

I am working with a mixture of AWS and Rackspace servers where the servers at the top will be on Rackspace, and the distribution server is in AWS, along with the edge clients (Wed Edition SQL Server). It looks like this...

Post #1529021
Posted Wednesday, January 08, 2014 11:35 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: 2 days ago @ 12:57 PM
Points: 461, Visits: 1,265
Just for additional clarity - the top tier of servers in Rackspace are the mirrored pair and Publication server(s).

The AWS domain contains the remote Distributor for Replication, and the systems I am calling edge clients with Wed Edition are the Subscribers.
Post #1529022
Posted Monday, January 13, 2014 6:55 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 11:51 AM
Points: 5,958, Visits: 12,839
SQL_ME_RICH (1/8/2014)
I've read that you can only have 1 distribution database per instance.

A publisher will only use a single distribution database, if that's what you're referring too?


SQL_ME_RICH (1/8/2014)
Is there any possibility to get 2 or more Distributors (distribution databases) to work in the same instance? Or is this just the way it is?

The instance you use as the ditributor can indeed have more than 1 distribution database, the distribution database may be called anything you like, it does not have to be called Distribution. See my screenshots below


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"


  Post Attachments 
Untitled.jpg (6 views, 52.51 KB)
Untitled2.jpg (4 views, 69.02 KB)
Untitled3.jpg (4 views, 69.95 KB)
Post #1530276
Posted Monday, January 13, 2014 9:32 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: 2 days ago @ 12:57 PM
Points: 461, Visits: 1,265
Hi Perry - Thank you for the reply. I should have made my question a bit more clear...Can the instance which is holding the Publisher database utilize more than 1 Distribution database. To date - my findings say no, but if you have information otherwise - I am all ears/eyes.

Thanks again!
Post #1530353
Posted Monday, January 13, 2014 11:51 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 11:51 AM
Points: 5,958, Visits: 12,839
SQL_ME_RICH (1/13/2014)
Hi Perry - Thank you for the reply. I should have made my question a bit more clear...Can the instance which is holding the Publisher database utilize more than 1 Distribution database. To date - my findings say no, but if you have information otherwise - I am all ears/eyes.

Thanks again!

I have edited my last post to display correctly, the answer is no


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1530401
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse