Dropping old SQL server name for replication

Question

Dropping old SQL server name for replication

kayin

SSC Rookie

Points: 38
More actions
December 14, 2008 at 12:54 am

#216579

Hi, need a hand ladies and gents.
Some has changed the name of a SQL server and now replication isn't working. I'm trying to create new publications however SQL server returns an error stating that the old server name still exists.
I've checked the master database and can see both the old and new SQL server names there.
When I try to dorp the old name, I just get a response stating that there are still remote login attached to the old name.
I'm trying to do this remotely by the way.
Any suggestions?
Thanks.
Kind regards,
Ka Kwok

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Adi Cohn-120898 SSC-Dedicated Points: 33944 More actions · Answer 1

You can try running sp_dropremotelogin old_name (Have to admit that I was never in this situation, so I never tried it).

Adi

--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

kayin SSC Rookie Points: 38 More actions · Answer 2

Mate thanks. I'll try that. Is there a way to see what remote logins are still associated with that server name?

That's one of the problems I have now.

Thanks.

Kind regards,

Ka Kwok

Adi Cohn-120898 SSC-Dedicated Points: 33944 More actions · Answer 3

I'd try to look at sys.remote_logins.

Adi

--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

kayin SSC Rookie Points: 38 More actions · Answer 4

Adi, Mate. I owe you a drink.

Anyway, now I'm stuck with the problem where if I'm trying to create a new publication, it still see's the old server name.

I'm wondering whether this might be a trusted connection issue.

Not sure whether the screen shot would come through.

Anyway, the problem is that it's trying to connect the server "B" and it's still seeing the server name "A".

Any suggestions?

Thanks.

Kind regards,

Ka Kwok

Adi Cohn-120898 SSC-Dedicated Points: 33944 More actions · Answer 5

Did you remember to run sp_addserver with the local parameter? If you didn't you should run the statement

exec sp_addserver 'NewName', 'local'

Adi

--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

yehuda klein SSC Rookie Points: 33 More actions · Answer 6

yehuda klein

SSC Rookie

Points: 33

December 15, 2008 at 1:58 pm

#912788

And restart the sql service.

kayin SSC Rookie Points: 38 More actions · Answer 7

Hi all, I appreciate the response back. To answer your questions, yeah did them all. Three times. The third time worked and nothings changed. I can't explain it.

I'm not worried about it now since it's running again. I just need to monitor the subscriptions now and make sure that they work.

Ka