New to Replication

I am new to replication. Please forgive me if this sounds silly.
I have one publisher and several subscriber, all in different locations. In
case of emergency and I have to shut down the publisher, I want to use the
one of the subscribers to process our business, and I want to turn this
subscriber to a new publisher. Is this possible? What kind of replication
should I use?
Its not really possible in SQL 2000, but it looks like the peer-to-peer
replication model in 2005.
You have to look at how the data flows. If it flows only from the publisher
to the subscribers it might be possible to convert a subscriber to a
publisher by applying the publication creation script on one of the
subscribers you wish to promote the new publisher. Then make all other
subscribers subscribers of this new publisher.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Wind" <Wind@.discussions.microsoft.com> wrote in message
news:4AF7A0BF-DB5F-43E8-BD2C-D7F1EE5E6098@.microsoft.com...
> I am new to replication. Please forgive me if this sounds silly.
> I have one publisher and several subscriber, all in different locations.
In
> case of emergency and I have to shut down the publisher, I want to use the
> one of the subscribers to process our business, and I want to turn this
> subscriber to a new publisher. Is this possible? What kind of replication
> should I use?
|||Thanks a lot for your reply.
Do you mean that if I am in SQL 2000, and the subscribers only read data,
not write, I should be able to turn one subscriber to a publisher? Actually,
what I want to do is, when the publisher has to be shut down (or damaged), I
will still have the full database for business continuity in another
location. This can be a kind of emergency backup system.
"Hilary Cotter" wrote:

> Its not really possible in SQL 2000, but it looks like the peer-to-peer
> replication model in 2005.
> You have to look at how the data flows. If it flows only from the publisher
> to the subscribers it might be possible to convert a subscriber to a
> publisher by applying the publication creation script on one of the
> subscribers you wish to promote the new publisher. Then make all other
> subscribers subscribers of this new publisher.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Wind" <Wind@.discussions.microsoft.com> wrote in message
> news:4AF7A0BF-DB5F-43E8-BD2C-D7F1EE5E6098@.microsoft.com...
> In
>
>
|||Yes you can do this, but its difficult. Basically you have to prep your
database on the subscriber.
IIRC you have to do the following
1) backup the publisher
2) restore it on the subscriber
3) change all identity columns to NFR
4) change all triggers to NFR
5) change all constraints to NFR
You may need to run DBCC checkident ('tableName', reseed,X) on some of the
subscriber tables to fix the identity property on the restored databases,
don't use the set identity_insert 'tableName', off in the insert procs
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Wind" <Wind@.discussions.microsoft.com> wrote in message
news:346FA462-5CD1-4156-BC06-E6B0662E4BFF@.microsoft.com...[vbcol=seagreen]
> Thanks a lot for your reply.
> Do you mean that if I am in SQL 2000, and the subscribers only read data,
> not write, I should be able to turn one subscriber to a publisher?
> Actually,
> what I want to do is, when the publisher has to be shut down (or damaged),
> I
> will still have the full database for business continuity in another
> location. This can be a kind of emergency backup system.
> "Hilary Cotter" wrote:
|||What about the alternate synchronization partner?
Jos.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23zmkjND0FHA.2960@.tk2msftngp13.phx.gbl...
> Its not really possible in SQL 2000, but it looks like the peer-to-peer
> replication model in 2005.
> You have to look at how the data flows. If it flows only from the
publisher[vbcol=seagreen]
> to the subscribers it might be possible to convert a subscriber to a
> publisher by applying the publication creation script on one of the
> subscribers you wish to promote the new publisher. Then make all other
> subscribers subscribers of this new publisher.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Wind" <Wind@.discussions.microsoft.com> wrote in message
> news:4AF7A0BF-DB5F-43E8-BD2C-D7F1EE5E6098@.microsoft.com...
> In
the[vbcol=seagreen]
replication
>
|||Plain merge and queued updating subscribers would also come into this
section, although none of these techniques would really allow the subscriber
to easily become the publisher.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)