November 13, 2006 at 1:32 am
Hello all,
One of my co-workers has pointed me this arena and I am finally here to get some answers to accomplish what I need to get done. I have a very simple setup with two SQL servers that sit in the same rack and I am trying to get them to where the DBs on the servers are exact images of each other so that in the case of failure, I would simply need to pull the network cable out of one and plug it into a second nic card on the other.
While trying to get this setup, I realized that SQL Server that is currently active was named local instead of the actual server name. So when I try to setup the replication an error pops up that simply states that you can not use a server name of local and to delete the registration and re-register as the actual server name. I have tried to find information on this on the net and simply do not see a detailed explanation of how to do this/what will happen when I do it. I see the selection to delete the registration but since we are currently not "redundant" I hesitate to move forward. Any information you all could provide would be appreciated.
Thanks in advance.
Shannon
November 14, 2006 at 8:40 am
shannon, it is safe to delete the registration of the server in enterprise manager as this is only a client conection the sql instance and not the instance itself. Then re-register it using the serrver name, which is the actual name of the default (or local) instance.
however if what you actually want is a warm standby server setup I would go for log shipping which is easier to setup and maintain then replication. the sql agents on the two boxes will need to run under the same domain account.
November 14, 2006 at 9:39 am
I agree. This is not a job for replication. The maintenance of replication will be a nightmare if you are making database schema changes on your source server (publisher).
November 14, 2006 at 9:47 am
Well, to explain why we are doing it this way briefly...I work at a TV Station and our play list databases are SQL databases so anytime there are changes to what is on air I want it to update automatically (transactional replication). That way if my main file server crashes I want to switch cables and be back online with the other databases. Broadcast is a lttle different than other industries so requirements are a little different. But I am willing to listen to other suggestions if everyone believes this to be the case
November 14, 2006 at 9:18 pm
1. You could register the server with a name (named pipes) and could easily setup the replication
2. In the scenario you have explanied, you could do a merge replication of the transactions between to two servers so that one of them can be used when the other is down. The moment other is up and running, data will be in sync.
3. Managing replication is quite simple & straight forward (we manage about 50 + databases with merge replication to a remote location)
rangark
November 15, 2006 at 8:23 am
OK I have deleted the original resgistration and made the name of the server the actual name of the PC. However when I go to set up my distributor, I keep getting a fail that says the username/password is incorrect. I created a un/pw that had admin rights to all db and changed the information to that utilize that, but still no avail. AM I missing something?
Thanks again!
Shannon
November 15, 2006 at 9:31 am
You should use 'sa' login to setup the replication. don't try use any other login for the replication setup process
rangark
November 15, 2006 at 9:47 am
I always use a Windows domain account with SQL Admin rights for replication, not a SQL account. If you use a SQL account, you may have to make sure the name & pwd are exactly the same on both machines.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply