Using Alias with Failover

5 Dec 2008 2:49 PM

deconinckg

In the following article Microsoft refers we can use a T-SQL script on a job
after failover, to change the alias.
http://technet.microsoft.com/en-us/library/dd207312.aspx

I didn't find out how to run a job after failover yet, but I'm more
willingly to know how you can change the Alias in registry through T-SQL.
Following this description it must be possible, but almost nowhere you can
find guidelines on how to really configure these in failover job to change it
all.

I'm hoping someone can help me out in this. Cause we would like a real
failover job without interference, and this alias might be the thing I'm
looking for.

So if you have any experience in this, please let me know. I would love to
know how the alias can be changed to go on different port and different
server so users only have to close client and reopen and login on new
principal.

8 Dec 2008 2:49 PM

deconinckg

Nobody that can help me?

Thing is that I really need this to be set up in test environment. We use
navision clients, and when we unplug the principal server we need to be sure
that clients only have to do a close client and reconnect. I'm wondering if
what I seek is the solution to this. Is it actually possible to use an alias
in this way that clients can log on to? So when a server fails that the alias
refers to the new principal server.

I'm still in education with SQL Server, but I like to dig deep sometimes. I
hope what I said isn't just jiberish, but that it can actually work that
clients just need a reconnect without rechanging the name of the server.

This is told to me from someone that in this case Alias is the way to do.
But I don't master that alias thing good yet. I know alias works on the same
machine, but not sure how it acts on a real server infrastructure. So if
anyone can give me some more intel in this I would gladly appreciate the help
and support ;)

Greetz

Show quoteHide quote

"deconinckg" wrote:

> In the following article Microsoft refers we can use a T-SQL script on a job
> after failover, to change the alias.
> http://technet.microsoft.com/en-us/library/dd207312.aspx
>
> I didn't find out how to run a job after failover yet, but I'm more
> willingly to know how you can change the Alias in registry through T-SQL.
> Following this description it must be possible, but almost nowhere you can
> find guidelines on how to really configure these in failover job to change it
> all.
>
> I'm hoping someone can help me out in this. Cause we would like a real
> failover job without interference, and this alias might be the thing I'm
> looking for.
>
> So if you have any experience in this, please let me know. I would love to
> know how the alias can be changed to go on different port and different
> server so users only have to close client and reopen and login on new
> principal.

9 Dec 2008 7:59 AM

Tibor Karaszi

I'm confused. The KB article you send refers to SharePoint, and it
doesn't talk about any type of alias. And in your subsequent post you
say you are using Navision. The short answer is that if your clients
supports database mirroring, then restarting the app is all needed
(assuming you have specified both partners name in the connection
string). This is in the end an application issue, so I suggest you
start with your application vendor.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi

Show quoteHide quote

"deconinckg" <deconin***@discussions.microsoft.com> wrote in message
news:EF20365C-0F96-4B4D-A2A0-EAB39E1EB5D9@microsoft.com...
> Nobody that can help me?
>
> Thing is that I really need this to be set up in test environment.
> We use
> navision clients, and when we unplug the principal server we need to
> be sure
> that clients only have to do a close client and reconnect. I'm
> wondering if
> what I seek is the solution to this. Is it actually possible to use
> an alias
> in this way that clients can log on to? So when a server fails that
> the alias
> refers to the new principal server.
>
> I'm still in education with SQL Server, but I like to dig deep
> sometimes. I
> hope what I said isn't just jiberish, but that it can actually work
> that
> clients just need a reconnect without rechanging the name of the
> server.
>
> This is told to me from someone that in this case Alias is the way
> to do.
> But I don't master that alias thing good yet. I know alias works on
> the same
> machine, but not sure how it acts on a real server infrastructure.
> So if
> anyone can give me some more intel in this I would gladly appreciate
> the help
> and support ;)
>
> Greetz
>
> "deconinckg" wrote:
>
>> In the following article Microsoft refers we can use a T-SQL script
>> on a job
>> after failover, to change the alias.
>> http://technet.microsoft.com/en-us/library/dd207312.aspx
>>
>> I didn't find out how to run a job after failover yet, but I'm more
>> willingly to know how you can change the Alias in registry through
>> T-SQL.
>> Following this description it must be possible, but almost nowhere
>> you can
>> find guidelines on how to really configure these in failover job to
>> change it
>> all.
>>
>> I'm hoping someone can help me out in this. Cause we would like a
>> real
>> failover job without interference, and this alias might be the
>> thing I'm
>> looking for.
>>
>> So if you have any experience in this, please let me know. I would
>> love to
>> know how the alias can be changed to go on different port and
>> different
>> server so users only have to close client and reopen and login on
>> new
>> principal.