Application Server to Point to Mirror Server

You must use SQL Native Client driver. This gives you the option to specify
the fail-over mirror server name. Then you must also use a witness server
for the fail-over to be automatic.
See books online;
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/a62d9dd7-3667-4751-a294-a61fc9caae7c.htm

Regards,
Dave Patrick ...Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Gary Lou" wrote:
> Hi All,
> I have tested database mirroring for a few days. The application server
> is using a connection string in the registry to point to SQL server.
> When failover happens, how can I tell the app server to failover and
> run against the mirrored server and mirrored database?
> Please advice. Thanks.
> -Gary
>
The other thing to keep in mind is that when the primary fails over the
connection closes with an error and the application server will have to
reopen the connection to get to the new primary. This may require some code
changes unless your application already handles this.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Dave Patrick" <DSPatrick@.nospam.gmail.com> wrote in message
news:382B1DEB-E7EB-4A6F-8AA8-C865A9215D05@.microsoft.com...
> You must use SQL Native Client driver. This gives you the option to
> specify the fail-over mirror server name. Then you must also use a witness
> server for the fail-over to be automatic.
> See books online;
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/a62d9dd7-3667-4751-a294-a61fc9caae7c.htm
>
> --
> Regards,
> Dave Patrick ...Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
> "Gary Lou" wrote:
>
|||Thank you for both of your response.
My application server is running on Windows 2000 sp4. I have SQL Native
Client enable in the SQL 2005 server.
Question:
1) I got a "Login timeout expired" error when tried to set up the
connection under ODBC. Do I need to install sqlncli.msi in the app
server to make it work?
2) The connection string in the registry is as below. What needs to be
changed to make the failover to work?
Provider=SQLOLEDB.1;Password=p8ssw0rd;Persist Security Info=True;User
ID=DB_USER1;Initial Catalog=MagicDB;Data Source=MagicSQL2000;Network
Library=DBMSSOCN
Many thanks.
Roger Wolter[MSFT] wrote:[vbcol=seagreen]
> The other thing to keep in mind is that when the primary fails over the
> connection closes with an error and the application server will have to
> reopen the connection to get to the new primary. This may require some code
> changes unless your application already handles this.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Dave Patrick" <DSPatrick@.nospam.gmail.com> wrote in message
> news:382B1DEB-E7EB-4A6F-8AA8-C865A9215D05@.microsoft.com...
|||You need either SQLNCLI or the .Net 2.0 SQL Client to use the failover
feature so you will have to install the appropriate software on your clients
I'm not a connection string expert. Obviously you will need to change the
provider to SQLNCLI and specify the secondary server. There's a good
explanation here:
http://msdn2.microsoft.com/de-de/library/ms366348.aspx
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Gary Lou" <garylou@.gmail.com> wrote in message
news:1165301726.681691.33270@.l12g2000cwl.googlegro ups.com...
> Thank you for both of your response.
> My application server is running on Windows 2000 sp4. I have SQL Native
> Client enable in the SQL 2005 server.
> Question:
> 1) I got a "Login timeout expired" error when tried to set up the
> connection under ODBC. Do I need to install sqlncli.msi in the app
> server to make it work?
> 2) The connection string in the registry is as below. What needs to be
> changed to make the failover to work?
> Provider=SQLOLEDB.1;Password=p8ssw0rd;Persist Security Info=True;User
> ID=DB_USER1;Initial Catalog=MagicDB;Data Source=MagicSQL2000;Network
> Library=DBMSSOCN
>
> Many thanks.
>
> Roger Wolter[MSFT] wrote:
>

Application Name

Hi
Does anyone know how the ODBC driver gets the application name that is
displayed by the SQL Server profiler? Our application does not explicitly
pass it in with the connection string but we are seeing a name under the
ApplicationName column in SQL Server profiler.
Many thanks
Shakti
I'm just curious. Does the application name that is generated make sense? I
know that if I don't set one in ADO.Net, the app name is something like ".net
client." If I need the information to say something that I really need to
set the AppName
Russel Loski, MCSD.Net
"Johnny" wrote:

> Hi
> Does anyone know how the ODBC driver gets the application name that is
> displayed by the SQL Server profiler? Our application does not explicitly
> pass it in with the connection string but we are seeing a name under the
> ApplicationName column in SQL Server profiler.
> Many thanks
> Shakti
>
>
|||Hi,
there are several way, one would be to tweak the connection string with
the appName parameter.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Agree that your suggestion is the way to set the application name but if it
is not set by the application where does it get the name from? I can see
the program name in the sysprocesses table but if the application is not
setting it explicitly where does it come from?
Thanks
Shakti
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1169569609.022799.219340@.l53g2000cwa.googlegr oups.com...
> Hi,
> there are several way, one would be to tweak the connection string with
> the appName parameter.
> HTH, Jens K. Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
|||Still from the application side. It's a parameter for the
connection string, property for the connection, different
ways depending on the application.Not all connections from
applications will supply them.
-Sue
On Tue, 23 Jan 2007 20:39:32 -0000, "johnny"
<prem14@.acm.org> wrote:

>Agree that your suggestion is the way to set the application name but if it
>is not set by the application where does it get the name from? I can see
>the program name in the sysprocesses table but if the application is not
>setting it explicitly where does it come from?
>Thanks
>Shakti
>"Jens" <Jens@.sqlserver2005.de> wrote in message
>news:1169569609.022799.219340@.l53g2000cwa.googleg roups.com...
>
|||We are going round in circles! Application is neither supplying the
application name parameter nor setting any connection property whatsoever.
So, where does ODBC driver / sql server / sysprocesses get the program name
from? It appears to have our company name!
Cheers
Shakti
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:m9hdr2h8qehp2c1q96jibubcmd44s900ht@.4ax.com...
> Still from the application side. It's a parameter for the
> connection string, property for the connection, different
> ways depending on the application.Not all connections from
> applications will supply them.
> -Sue
> On Tue, 23 Jan 2007 20:39:32 -0000, "johnny"
> <prem14@.acm.org> wrote:
>
|||Client would have been the better word to use rather than
application. It depends on what application.you are using.
And driver.
-Sue
On Wed, 24 Jan 2007 11:30:36 -0000, "Johnny"
<prem14@.acm.org> wrote:

>We are going round in circles! Application is neither supplying the
>application name parameter nor setting any connection property whatsoever.
>So, where does ODBC driver / sql server / sysprocesses get the program name
>from? It appears to have our company name!
>Cheers
>Shakti
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:m9hdr2h8qehp2c1q96jibubcmd44s900ht@.4ax.com.. .
>

Application Name

Hi
Does anyone know how the ODBC driver gets the application name that is
displayed by the SQL Server profiler? Our application does not explicitly
pass it in with the connection string but we are seeing a name under the
ApplicationName column in SQL Server profiler.
Many thanks
ShaktiI'm just curious. Does the application name that is generated make sense?
I
know that if I don't set one in ADO.Net, the app name is something like ".ne
t
client." If I need the information to say something that I really need to
set the AppName
--
Russel Loski, MCSD.Net
"Johnny" wrote:

> Hi
> Does anyone know how the ODBC driver gets the application name that is
> displayed by the SQL Server profiler? Our application does not explicitly
> pass it in with the connection string but we are seeing a name under the
> ApplicationName column in SQL Server profiler.
> Many thanks
> Shakti
>
>|||Hi,
there are several way, one would be to tweak the connection string with
the appName parameter.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--|||Agree that your suggestion is the way to set the application name but if it
is not set by the application where does it get the name from? I can see
the program name in the sysprocesses table but if the application is not
setting it explicitly where does it come from?
Thanks
Shakti
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1169569609.022799.219340@.l53g2000cwa.googlegroups.com...
> Hi,
> there are several way, one would be to tweak the connection string with
> the appName parameter.
> HTH, Jens K. Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>|||Still from the application side. It's a parameter for the
connection string, property for the connection, different
ways depending on the application.Not all connections from
applications will supply them.
-Sue
On Tue, 23 Jan 2007 20:39:32 -0000, "johnny"
<prem14@.acm.org> wrote:

>Agree that your suggestion is the way to set the application name but if it
>is not set by the application where does it get the name from? I can see
>the program name in the sysprocesses table but if the application is not
>setting it explicitly where does it come from?
>Thanks
>Shakti
>"Jens" <Jens@.sqlserver2005.de> wrote in message
>news:1169569609.022799.219340@.l53g2000cwa.googlegroups.com...
>|||We are going round in circles! Application is neither supplying the
application name parameter nor setting any connection property whatsoever.
So, where does ODBC driver / sql server / sysprocesses get the program name
from? It appears to have our company name!
Cheers
Shakti
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:m9hdr2h8qehp2c1q96jibubcmd44s900ht@.
4ax.com...
> Still from the application side. It's a parameter for the
> connection string, property for the connection, different
> ways depending on the application.Not all connections from
> applications will supply them.
> -Sue
> On Tue, 23 Jan 2007 20:39:32 -0000, "johnny"
> <prem14@.acm.org> wrote:
>
>|||Client would have been the better word to use rather than
application. It depends on what application.you are using.
And driver.
-Sue
On Wed, 24 Jan 2007 11:30:36 -0000, "Johnny"
<prem14@.acm.org> wrote:

>We are going round in circles! Application is neither supplying the
>application name parameter nor setting any connection property whatsoever.
>So, where does ODBC driver / sql server / sysprocesses get the program name
>from? It appears to have our company name!
>Cheers
>Shakti
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:m9hdr2h8qehp2c1q96jibubcmd44s900ht@.
4ax.com...
>