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 |
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2006-08-30 : 10:48:29
|
Dave writes "I have recently taken control of a sql 2000 cluster and a sql 2005 cluster each comprising 2 nodes configured active/passive.I have a requirement to replicate data from these clusters to other SQL Servers but have hit somthing of a brick wall in both cases as detailed below.1.SQL 2005 issueThe replication wizard requires that you specify a particular server (i.e. Node) rather than use the virtual sql server name or an IP address as these aren't supported.How do I overcome this as specifying an individual node will surely halt replication in the event of failover?2. SQL 2005 IssueWhen configuring the SQL 2000 replication I get an ERROR 18483 'distributor_admin' is not defined as a remote login at the server. I would like this cluster to act as both distributor and publisher.Is this a problem with the location of the distribution databaseand if so where should this be located? Should I set it up in the default location or should it be located on a shared resource along with the snapshot folder?The SQLSERVERAGENT service runs under a domain account which is also set up as a local administrator on all nodes in the cluster.I have very limited experience with clusters and can not find anything in BOL or other sources on replication involving clusters so any guidance will be greatly appreciated.Dave" |
|
Rishi Maini SQL2K5 Admin
Yak Posting Veteran
80 Posts |
Posted - 2006-08-31 : 03:02:16
|
Do "select @@servername" on the Cluster and make sure that you get the right "Virtual SQL Server" Name. If not "sp_dropserver" and "sp_addserver: can be used to rectify the Server Name (Check BOL to get an insight of these two SP). Furthermore make sure that the ID of the Local Server is set to "0" in "sysservers"ThanksRishi Maini |
|
|
|
|
|