Similar to "Simplest way to move an entrie database"

[mj]

My question is similar to "Simplest way to move an entire database".

I have to move a central publisher (win2K server)
to a new physical server with no down time.
The current setup is a standalone that houses it's own
domain, web, database and application.

I need to migrate this to a database server (win2k5).

2 approaches

Path 1
install and configure the Win2k5 on the new database server.
Script the replicated databases on the old server
Execute the scripts on the new server.
then (This is where I am lost)
somehow make the new database server an alternate publisher?
At some time in the near future, Somehow make the alternate publisher
the central publisher.

Path 2
make the new database server a central publisher and rebuild all publications.

Are there any references for this scenario?

Thanks MJ

[Hilary Cotter]

I assume this is transactional replication.

What is unclear to me is data flow. Right now you are banging away at the
central publisher (SQL 2000). At some point in time you will move the new
central publisher SQL 2005. How is this cutover going to occur with no
downtime?

What I think you need to do is make the current central publisher replicate
to the new SQL 2005 machine. Have the SQL 2005 machine configured to
replicate to the remote subscribers, but don't create the subscriptions yet.
Have this in a script.

When you are ready to go, point the users who are using the central
publisher to the new central publisher and run the script. As there must be
some downtime associated with this or perhaps you can configure parallel
feeds you should be able to time this to eliminate data loss to the remote
subscribers. I.e. stop the users, create the subscriptions, and then repoint
the users.

--
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
"mj" <m...@discussions.microsoft.com> wrote in message
news:35038344-78D1-4093...@microsoft.com...

[mj]

Hi Hilary;

This is Merge replication with Push and Pull subscriptions.
I read microsoft article how to setyup "alternate synchronization partner"
yesterday and am going to make a stab at testing this today.

If this works then I think I can "fail over" to the alternate partner.

It looks like I can do this with minimum impact.

[Hilary Cotter]

Kind of. It really is intended to act as a temporary publisher while the
real one is offline. The subscribers must be manually repointed to the
original publisher before the retention period expires, automatic identity
range management won't increment, and there are a few other caveats that you
have to watch out for.

--
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
"mj" <m...@discussions.microsoft.com> wrote in message

news:DB6215C5-CB5E-4B25...@microsoft.com...