Replication: Transactional: Multi Publications, One Subscriber.

Greetings All, I was hoping that a replication sage might be able to
answer a question for me.

I want to have one subscriber subscribing to N publishers. I
essentially have a company that has a main headquarters and three
satellite offices. I want each of the satellite offices to push their
data up to the master database. From what I have read it seems like
this should not be a problem. Some questions that come to mind are:

1.)Does the master need to be read only or can it be configured to be
updateable as well?
2.)Can the distribution agent on all the publishers be set to
continuously distribute or should it be staggered so as not to cause a
problem when another distribution agent is running?
3.)If the distribution is set to "delay distribution" will this cause
changes on the subscriber to be pushed out to the publishers?

In this database guid's are used as pk's so the issue of pk collisions
is not a problem.

I hope that this question is not too vague. My experience thus far
with replication has been simple one way transactional and simple
merge replication.

Regards, Louis Frolio"Louis Frolio" <froliol@.yahoo.com> wrote in message
news:94c28610.0409221536.67fda321@.posting.google.c om...
> Greetings All, I was hoping that a replication sage might be able to
> answer a question for me.
> I want to have one subscriber subscribing to N publishers. I
> essentially have a company that has a main headquarters and three
> satellite offices. I want each of the satellite offices to push their
> data up to the master database. From what I have read it seems like
> this should not be a problem. Some questions that come to mind are:
> 1.) Does the master need to be read only or can it be configured to be
> updateable as well?
> 2.) Can the distribution agent on all the publishers be set to
> continuously distribute or should it be staggered so as not to cause a
> problem when another distribution agent is running?
> 3.) If the distribution is set to "delay distribution" will this cause
> changes on the subscriber to be pushed out to the publishers?
>
> In this database guid's are used as pk's so the issue of pk collisions
> is not a problem.
> I hope that this question is not too vague. My experience thus far
> with replication has been simple one way transactional and simple
> merge replication.
> Regards, Louis Frolio

You might want to post this in microsoft.public.sqlserver.replication, where
there are probably more replication sages than in this newsgroup.

Simon|||froliol@.yahoo.com (Louis Frolio) wrote in message news:<94c28610.0409221536.67fda321@.posting.google.com>...
> Greetings All, I was hoping that a replication sage might be able to
> answer a question for me.
> I want to have one subscriber subscribing to N publishers. I
> essentially have a company that has a main headquarters and three
> satellite offices. I want each of the satellite offices to push their
> data up to the master database. From what I have read it seems like
> this should not be a problem. Some questions that come to mind are:
> 1.)Does the master need to be read only or can it be configured to be
> updateable as well?
> 2.)Can the distribution agent on all the publishers be set to
> continuously distribute or should it be staggered so as not to cause a
> problem when another distribution agent is running?
> 3.)If the distribution is set to "delay distribution" will this cause
> changes on the subscriber to be pushed out to the publishers?
>
> In this database guid's are used as pk's so the issue of pk collisions
> is not a problem.
> I hope that this question is not too vague. My experience thus far
> with replication has been simple one way transactional and simple
> merge replication.
> Regards, Louis Frolio

Q #1
> 1.)Does the master need to be read only or can it be configured to be
> updateable as well?

A. The subscriber database can be updated by users on that end, it
does not need to be read only.

Q #2
> continuously distribute or should it be staggered so as not to cause a
> problem when another distribution agent is running?

A. It can be done either way without issue.

Q #3
> 3.)If the distribution is set to "delay distribution" will this cause
> changes on the subscriber to be pushed out to the publishers?

A. No.

All, I have answered my own questions since I posted this missive.|||"Simon Hayes" <sql@.hayes.ch> wrote in message news:<4152b7ee_1@.news.bluewin.ch>...
> "Louis Frolio" <froliol@.yahoo.com> wrote in message
> news:94c28610.0409221536.67fda321@.posting.google.c om...
> > Greetings All, I was hoping that a replication sage might be able to
> > answer a question for me.
> > I want to have one subscriber subscribing to N publishers. I
> > essentially have a company that has a main headquarters and three
> > satellite offices. I want each of the satellite offices to push their
> > data up to the master database. From what I have read it seems like
> > this should not be a problem. Some questions that come to mind are:
> > 1.) Does the master need to be read only or can it be configured to be
> > updateable as well?
> > 2.) Can the distribution agent on all the publishers be set to
> > continuously distribute or should it be staggered so as not to cause a
> > problem when another distribution agent is running?
> > 3.) If the distribution is set to "delay distribution" will this cause
> > changes on the subscriber to be pushed out to the publishers?
> > In this database guid's are used as pk's so the issue of pk collisions
> > is not a problem.
> > I hope that this question is not too vague. My experience thus far
> > with replication has been simple one way transactional and simple
> > merge replication.
> > Regards, Louis Frolio
> You might want to post this in microsoft.public.sqlserver.replication, where
> there are probably more replication sages than in this newsgroup.
> Simon

Simon, thanks I did not realize that that group existed.

L