High availability for Database Mirroring

Hello,

I would like implementing a database mirroring architecture with SQL server 2005 but i have questions.

If i don't use a cluster architecture, i would like knowing if there's any solution to move the alias SQL server from the primary to the secondary by script.

Anyone got a pb like me? or any solution?...

Thanks for your help...

You mean you'd like to have the two servers have the same name?

|||

Well...

On SQL 2005 the alias SQL server name stay on the server and don't go up in the WINS. With the graphic administration, we can directly add or modify this alias.

The best way for me should be to get an alias being moved by script in order to be used on the primary server.

As we can change this alias by a graphical MMC, so i guess we can change it by script no?

|||I don't see how switching the alias will help you without some other background work being set up first. As luck would have it, I'm contemplating this same issue, so perhaps my reply will provide enough provocation for someone else to come along and answer this to both our satisfactions...

First, as far as the alias goes... Suppose we have a production server, 10.1.2.1 and a 'hot-standby' server, 10.1.2.2. Now further, suppose our alias is 'SQLSRVR' = 10.1.2.1.
Now, assume something bad happens. If one simply goes into the alias and changes the mapping to 10.1.2.2, what does that get you? Answer, nothing you want - unless in the background you have been shipping the logs or in some other way, trickling over the transactions that have been going on for 10.1.2.1.

What I'm contemplating is this - 10.1.2.1 is up and running and attached to a SAN. 10.1.2.2 is up and running and attached to the same SAN. Both servers have their 'own' logical volumes - say - one for mdf/trn; one for ldg/bak; and one for tempdb. Assume the SQL Server software is installed on the servers internal drives. They can both see the other's volumes, but since they are in effect running their own instances, the id's for objects will be unique to each system (I'm not clustering).

Now, through some mechanism, we need to on some time interval, trickle over the transactions that have occurred on 10.1.2.1 to 10.1.2.2. My question is this - what is the best way on 2005 to do this 'trickle'? Log shipping. mirroring, what?

Can someone provide input here? Thanks in advance.

randyvol|||

Actually, I believe that what you are asking for is built into mirroring if you run in synchronous mode.

You can build your application with a connection string that names both mirror instances, and will transparently fail over to the secondary if the primary cannot be reached. In synchronous mode, the failover can be accomplished entirely automatically, with no scripting required, or on command.

Is there something additional that you need which I'm missing?

|||

I can't change connection string because i'm using a software not developped by me.

I'll send a request to the support of this program.

I found on this site the solution to my problem by changing alias in the registry

http://blogs.developpeur.org/christian/archive/2006/11/04/SQL-Server-_3A00_-Alias-de-serveurs.aspx

Thanks you all for your answers...