"Wojtek Z" <wojtas_z@poczta.fm> wrote in message
news:cgv19k$r68$1@atlantis.news.tpi.pl...
> I would like to create a merge replication between few db, but
> I want to keep the replication even if Publisher would be out of order for
> some time.
> How can I co that? I'm thinking about creating one of subscribers a new
> publisher - is it a good idea ?
>
> What would You suggest ? What is most reliable ?
>
> Best Regards
> Wojciech Znaniecki
>
>

"Wojtek Z" <wojtas_z@poczta.fm> wrote in message
news:cgv5cg$hr9$1@nemesis.news.tpi.pl...
> Thanks for fast anwsering :)
>
> Well what I wanted to do was something like that :
>
> Serv1 is a publisher and a distributor, Serv2 & Serv3 are Subscribers.
> But in something is wrong with Serv1 Serv2 and Serv3 cant exchange their
> data.
> I would like to prevent that.
>
> In another way : When one of 3 servers is off-line the other 2 have to
keep
> exchanging their data
>
> Best Regards
> Wojciech Znaniecki
>
> U¿ytkownik "Hilary Cotter" <hilaryk@att.net> napisa³ w wiadomo¶ci
> news:O01tuYojEHA.3428@TK2MSFTNGP11.phx.gbl...
> > I think what you are talking about is the retention period.
> >
> > After you have created your publication if you right click on it and
> select
> > properties, and in the general tab you will see a Subscription
Expiration
> > dialog. You can set how long you want your subscribers to remain off
line
> > before the subscription expires or is dropped here. Make sure you also
go
> > to tools, point to replication, click Configure Publishers, Subscribers,
> and
> > Distributors and in the distributor tab, click on properties, and in the
> > history retention, match whatever you set in the publication properties
> > susbcription expiration with this value here.
> >
> > The downside of having long retention periods is that more data will go
> over
> > the wire when your subscriber/publisher comes back on line, and
sometimes
> > its faster to merely generate and deploy a new snapshot.
> >
> > Your choice depends on the stability of your servers and links as well
as
> > the number of transactions. For reliable links and servers 5 days is
> pretty
> > good.
> >
> > --
> > Hilary Cotter
> > Looking for a book on SQL Server replication?
> > http://www.nwsu.com/0974973602.html
> >
> >
> > "Wojtek Z" <wojtas_z@poczta.fm> wrote in message
> > news:cgv19k$r68$1@atlantis.news.tpi.pl...
> > > I would like to create a merge replication between few db, but
> > > I want to keep the replication even if Publisher would be out of order
> for
> > > some time.
> > > How can I co that? I'm thinking about creating one of subscribers a
new
> > > publisher - is it a good idea ?
> > >
> > > What would You suggest ? What is most reliable ?
> > >
> > > Best Regards
> > > Wojciech Znaniecki
> > >
> > >
> >
> >
>
>

> I think what you are talking about is the retention period.
>
> After you have created your publication if you right click on it and
select
> properties, and in the general tab you will see a Subscription Expiration
> dialog. You can set how long you want your subscribers to remain off line
> before the subscription expires or is dropped here. Make sure you also go
> to tools, point to replication, click Configure Publishers, Subscribers,
and
> Distributors and in the distributor tab, click on properties, and in the
> history retention, match whatever you set in the publication properties
> susbcription expiration with this value here.
>
> The downside of having long retention periods is that more data will go
over
> the wire when your subscriber/publisher comes back on line, and sometimes
> its faster to merely generate and deploy a new snapshot.
>
> Your choice depends on the stability of your servers and links as well as
> the number of transactions. For reliable links and servers 5 days is
pretty
> good.
>
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
>
> "Wojtek Z" <wojtas_z@poczta.fm> wrote in message
> news:cgv19k$r68$1@atlantis.news.tpi.pl...
> > I would like to create a merge replication between few db, but
> > I want to keep the replication even if Publisher would be out of order
for
> > some time.
> > How can I co that? I'm thinking about creating one of subscribers a new
> > publisher - is it a good idea ?
> >
> > What would You suggest ? What is most reliable ?
> >
> > Best Regards
> > Wojciech Znaniecki
> >
> >
>
>

> Another way to do this, which will work under limited situations is to do
> republishing. Server 1 publishes to Server 2. Server 2 publishes to Server

> I think you want to look at alternate sync partners. This is not an
> automatic process you have to do some work to configure this.
>
> This will not enable Server 2 and Server 3 to communicate with each other
> while Server1 is offline. What this involves is a new server Server 4,
which
> acts as the publisher until server 1 comes back on.
>
> Another way to do this, which will work under limited situations is to do
> republishing. Server 1 publishes to Server 2. Server 2 publishes to Server
1.
>
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
>
> "Wojtek Z" <wojtas_z@poczta.fm> wrote in message
> news:cgv5cg$hr9$1@nemesis.news.tpi.pl...
> > Thanks for fast anwsering :)
> >
> > Well what I wanted to do was something like that :
> >
> > Serv1 is a publisher and a distributor, Serv2 & Serv3 are Subscribers.
> > But in something is wrong with Serv1 Serv2 and Serv3 cant exchange their
> > data.
> > I would like to prevent that.
> >
> > In another way : When one of 3 servers is off-line the other 2 have to
> keep
> > exchanging their data
> >
> > Best Regards
> > Wojciech Znaniecki
> >
> > U¿ytkownik "Hilary Cotter" <hilaryk@att.net> napisa³ w wiadomo¶ci
> > news:O01tuYojEHA.3428@TK2MSFTNGP11.phx.gbl...
> > > I think what you are talking about is the retention period.
> > >
> > > After you have created your publication if you right click on it and
> > select
> > > properties, and in the general tab you will see a Subscription
> Expiration
> > > dialog. You can set how long you want your subscribers to remain off
> line
> > > before the subscription expires or is dropped here. Make sure you
also
> go
> > > to tools, point to replication, click Configure Publishers,
Subscribers,
> > and
> > > Distributors and in the distributor tab, click on properties, and in
the
> > > history retention, match whatever you set in the publication
properties
> > > susbcription expiration with this value here.
> > >
> > > The downside of having long retention periods is that more data will
go
> > over
> > > the wire when your subscriber/publisher comes back on line, and
> sometimes
> > > its faster to merely generate and deploy a new snapshot.
> > >
> > > Your choice depends on the stability of your servers and links as well
> as
> > > the number of transactions. For reliable links and servers 5 days is
> > pretty
> > > good.
> > >
> > > --
> > > Hilary Cotter
> > > Looking for a book on SQL Server replication?
> > > http://www.nwsu.com/0974973602.html
> > >
> > >
> > > "Wojtek Z" <wojtas_z@poczta.fm> wrote in message
> > > news:cgv19k$r68$1@atlantis.news.tpi.pl...
> > > > I would like to create a merge replication between few db, but
> > > > I want to keep the replication even if Publisher would be out of
order
> > for
> > > > some time.
> > > > How can I co that? I'm thinking about creating one of subscribers a
> new
> > > > publisher - is it a good idea ?
> > > >
> > > > What would You suggest ? What is most reliable ?
> > > >
> > > > Best Regards
> > > > Wojciech Znaniecki
> > > >
> > > >
> > >
> > >
> >
> >
>
>