Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
blindman
Master Smack Fu Yak Hacker
2365 Posts |
 Posted - 2010-11-09 : 12:50:33
|
| I'm trying to set up snapshot replication between two servers (SQL Server 2005).It does not matter to me which server is the publisher, and which is the subscriber.Problem is, either way I attempt to set up the replication, the set up fails because one of the server's configured servername is not its actual servername, and the replication wizard absolutely refused to connect to it.In other words, when I run this on the offending server: SELECT @@SERVERNAME SELECT SERVERPROPERTY('ServerName')I get different results:HCXXXHC1XXXThe configuration manager shows HCXXX as an alias for server HC1XXX.Now, supposedly I can rename the server like so:USE MASTERGOSP_DROPSERVER 'HCXXX'GOUSE MASTERGOSP_ADDSERVER 'HC1XXX', 'LOCAL'GOBut I am worried. What, if anything, might be trying to connect under the old server name, and might fail if I execute the SP_DROPSERVER and SP_ADDSERVER commands? Are there any other things I should be concerned about before issuing these commands?________________________________________________If it is not practically useful, then it is practically useless.________________________________________________ |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
SP_DROPSERVER hazards.