|
Home > Archive > MS SQL Server Replication > October 2006 > Setting up replication with virtual server name
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Setting up replication with virtual server name
|
|
|
| We are trying to setup merge replication on a virtual server, but it
keeps failing. We have run "sp_helpserver", "sp_dropserver
'localmachinename'", and "sp_addserver 'virtualservername',
'local'" to
ensure that SQL Server will use the virtual server name, but the setup
still fails. We have also tried adding the virtual server name as an
alias in the Client Network Utility.
Does anyone have any other suggestions on how to fix it so that we can
get the replication setup using the virtual servername?
We are on SQL Server 2000. The reason we need to use a virtual server
name is because we are using SteelEye LifeKeeper clustering software.
We have contacted them with support but so far their help has been
limited.
Thanks,
Peter
| |
| Hilary Cotter 2006-10-25, 6:03 am |
| Replication needs the netbios name to be whatever is returned by select
@@servername. So setting it to something different won't work.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"Peter" <peter_kwas@yahoo.ca> wrote in message
news:1161200133.454055.226770@f16g2000cwb.googlegroups.com...
> We are trying to setup merge replication on a virtual server, but it
> keeps failing. We have run "sp_helpserver", "sp_dropserver
> 'localmachinename'", and "sp_addserver 'virtualservername',
'local'" to
> ensure that SQL Server will use the virtual server name, but the setup
> still fails. We have also tried adding the virtual server name as an
> alias in the Client Network Utility.
>
> Does anyone have any other suggestions on how to fix it so that we can
> get the replication setup using the virtual servername?
>
> We are on SQL Server 2000. The reason we need to use a virtual server
> name is because we are using SteelEye LifeKeeper clustering software.
> We have contacted them with support but so far their help has been
> limited.
>
> Thanks,
> Peter
>
|
|
|
|
|