Moving subscriber to a new server

Hi,
environment:
SQL Server 2000 EE, SP4, latest security update on win 2003. Using merge PULL
replication.one Publisher, 2 subscribers.
We have a need to move a DB with a pull subscription to a new
server. The new server will be setup on the same network with the same name as
the old one. (publisher on a different network)
after moving the database (detach,attach ,subscriptiom need to be deleted to
do this) and if the publisher has new data inserted during the move how can I
get the subscriber on the new server to synch with publisher and get the data
changes.
CTS DBA
hey can anybody please help?
I got till this Monday only to come up with the solution
CTS DBA
"CTS_DBA" wrote:

> Hi,
> environment:
> SQL Server 2000 EE, SP4, latest security update on win 2003. Using merge PULL
> replication.one Publisher, 2 subscribers.
> We have a need to move a DB with a pull subscription to a new
> server. The new server will be setup on the same network with the same name as
> the old one. (publisher on a different network)
> after moving the database (detach,attach ,subscriptiom need to be deleted to
> do this) and if the publisher has new data inserted during the move how can I
> get the subscriber on the new server to synch with publisher and get the data
> changes.
> --
> CTS DBA
|||Have a look at @.allow_subscription_copy which is a property of the
publication. It can be set to allow copying of subscriber databases. Can't
test your particular requirements at the moment, but please give it a go.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||thanks paul,
copying subscription works for dbs less than 2GB, mine is 12Gb.
I'm still testing this but looks like it's working,
synch the subscriber with the publication,
run the snapshot agant
make a copy of the db and move it to the new server
create a new subscription.
the new subscription will captures changes since the last back up
any body has any commnets?
"Paul Ibison" wrote:

> Have a look at @.allow_subscription_copy which is a property of the
> publication. It can be set to allow copying of subscriber databases. Can't
> test your particular requirements at the moment, but please give it a go.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>

Moving SQL2000 to SQL2005 - COM+ Transaction Issue

I am trying to move an application that is currently using SQL2000 to SQL2005

Production environment:

Server1: Win 2000/SQL2000
Server2: Win 2003/IIS/COM+ & ASP

Trying to move to:

Server1: Win 2003/SQL2005
Server2: Win 2003/IIS/COM+ & ASP

The problem is that when a COM+ control tries to start up a transaction I keep getting the following error: error '8004d00a': New transaction cannot enlist in the specified transaction coordinator

I have discovered a ton of articles, blogs, etc. that suggest setting up security in component services, the firewall, testing with DTCPing (which works fine) and more but it seems that they were all talking about Win2003 and SQL2000. I cannot find anything that specifically references SQL2005.

I have modified both servers with all of the suggestions including the firewall (which is turned off BTW) but to no avail.

Has anyone run into this problem with SQL2005 and hopefully solved it?

Thanks,

Mark

I'm having the same problem... no resolution yet.

Using profiler I can tell that DTC is reaching SQL.

|||

I actually figured out the problem (in my case). I was working within a test environment using 2 Virtual Servers. The problem was that the two servers were copied from the same base server image (without being sysprep'd) so they had identical identifiers throughout the system. When I created a brand new server and hooked everything up and followed all of the recommended setups it started working. My problem had nothing to do with SQL200 vs SQL2005.

The big clue came when I ran the DCOM "ping" app. It said that communication was working but the DCOM ID's were identical and that may cause a problem - and it did.

Good luck.

Moving SQL 2000 cluster to a different domain

Dear all,
We need to move SQL 2000 Cluster on Win 2003 server box from test to prod
domain. What are the steps we need to follow to make sure SQL 2000 cluster is
up and running in the new domain. I know that we need to change the service
account from window services. Can we change the IP address directly from the
cluster administration window. Any help or link to KM is appreciated.
Thanks
Chinna.
I found the following kb article
http://support.microsoft.com/default...b;en-us;319016
Is this enough to do the task
Thanks in advance!
Chinna.
"Chinna Kondaveeti" wrote:

> Dear all,
> We need to move SQL 2000 Cluster on Win 2003 server box from test to prod
> domain. What are the steps we need to follow to make sure SQL 2000 cluster is
> up and running in the new domain. I know that we need to change the service
> account from window services. Can we change the IP address directly from the
> cluster administration window. Any help or link to KM is appreciated.
> Thanks
> Chinna.