How to connect to a mirrored SQL Server?

SQL Configuration: Two 2003 Servers (OS Std ver) with SQL 2005 (Std ver) configured for db mirroring. (The servers aren't clustered.)

Web.config configuration string is using "ServerA".

If we fail Server A, then Server B will change roles to "primary" in about 20 seconds (we have confirmed this via SQL Mgt Console). BUT...our web app is still pointing to Server A and doesn't seem to know there is a fail over. SO - how can I make the web app aware of the failure?

Server A and Server B aren't in a cluster - and I understand a cluster's virtual server would be referenced in the connection string. Is there a way to make the web app automatically switch to Server B (without a cluster configuration)?

From what I understand, the cluster configuration would require Ent Ed. of OS and SQL and a big fat check!!

Thanks.

-Kevin

One problem Database Mirroring did not make it to SQL Server 2005 shipping but expected in a service pack in the future. In the mean time Cluster is the way to go. Hope this helps.|||

I understand the mirror feature is for "testing only" - which is what I am doing. I have read that SQL 2005 SP1 would be released in early 2006 and MS would fully support the mirror capability.

From what I have read about mirroring, it seems that server clustering isn't necessary - that SQL can mirror the data. From a ASP.NET perspective, I just didn't know how it would know if a server is down and "switch" the connection to the failover server. Cluster's Vitual server makes that seamless - maybe that is the only way for ASP.NET apps to work with the failover server??

So, to clarify what I intended...how can ASP.Net use the failover server unless you are a cluster or unless you modify the connection string when Server A fails?

-Kevin

|||

SQL Server 2000 came with Log Shipping which is what Microsoft improved to get database Mirroring but you still need the Enterprise edition to get all fancy components of SQL Server. And for how to know when the server is down you will need monitoring tools like MOM (Microsoft Operation Management ) server or database specific tools like Embarcadero, I have used both and the cost is almost the same with basic cluster hardware without the System admin requirement. I would add the MOM implementation was enterprise wide so the cost was very high. Hope this helps.

How to configure up to 2G memory

I have a SQL 2000 Enterprise server on a Windows 2003 Standard Edition.
Seem I can only use 4GB max for SQL. How can I do the configuration for
enable above 2GB memeory from both windows and SQL server perspective.
/AWE, /3GB, /PAE for boot.ini ?
sp_configure 'awe enable', 1
sp_configure 'max server memory' , 4096 ? ?
How to configure memory for more than 2 GB in SQL Server
http://support.microsoft.com/kb/274750/
AMB
"HG" wrote:

> I have a SQL 2000 Enterprise server on a Windows 2003 Standard Edition.
> Seem I can only use 4GB max for SQL. How can I do the configuration for
> enable above 2GB memeory from both windows and SQL server perspective.
> /AWE, /3GB, /PAE for boot.ini ?
> sp_configure 'awe enable', 1
> sp_configure 'max server memory' , 4096 ? ?
>
sql

How to configure up to 2G memory

I have a SQL 2000 Enterprise server on a Windows 2003 Standard Edition.
Seem I can only use 4GB max for SQL. How can I do the configuration for
enable above 2GB memeory from both windows and SQL server perspective.
/AWE, /3GB, /PAE for boot.ini '
sp_configure 'awe enable', 1
sp_configure 'max server memory' , 4096 ? ?How to configure memory for more than 2 GB in SQL Server
http://support.microsoft.com/kb/274750/
AMB
"HG" wrote:

> I have a SQL 2000 Enterprise server on a Windows 2003 Standard Edition.
> Seem I can only use 4GB max for SQL. How can I do the configuration for
> enable above 2GB memeory from both windows and SQL server perspective.
> /AWE, /3GB, /PAE for boot.ini '
> sp_configure 'awe enable', 1
> sp_configure 'max server memory' , 4096 ? ?
>

How to configure up to 2G memory

I have a SQL 2000 Enterprise server on a Windows 2003 Standard Edition.
Seem I can only use 4GB max for SQL. How can I do the configuration for
enable above 2GB memeory from both windows and SQL server perspective.
/AWE, /3GB, /PAE for boot.ini '
sp_configure 'awe enable', 1
sp_configure 'max server memory' , 4096 ? ?How to configure memory for more than 2 GB in SQL Server
http://support.microsoft.com/kb/274750/
AMB
"HG" wrote:
> I have a SQL 2000 Enterprise server on a Windows 2003 Standard Edition.
> Seem I can only use 4GB max for SQL. How can I do the configuration for
> enable above 2GB memeory from both windows and SQL server perspective.
> /AWE, /3GB, /PAE for boot.ini '
> sp_configure 'awe enable', 1
> sp_configure 'max server memory' , 4096 ? ?
>

How to configure ports in SQL server configuration manager

Hi,
unfortunately I mixed up the ip settings in SQL server configuration manager
(I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
have an event in the application protocol (3), it says that configuration for
SQL instances "bkupexec" and "sqlexpress" are invalid.
I tried 100 different settings in SQL configuratin manager, but the events
are remaining. I cannot find out to configure this. Backup Exce for example
has nothing where I could configure a port address for communicating with its
SQL instance.
Can someone provide me with information about what to configure in SQL
Server Configuration Manager (and probably in Backup Exec - Symantec did not
answer until now) to avoid the error messages?
Thanx in advance,
Tim
Hi
"Tim Meltzer" wrote:

> Hi,
> unfortunately I mixed up the ip settings in SQL server configuration manager
> (I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
> have an event in the application protocol (3), it says that configuration for
> SQL instances "bkupexec" and "sqlexpress" are invalid.
> I tried 100 different settings in SQL configuratin manager, but the events
> are remaining. I cannot find out to configure this. Backup Exce for example
> has nothing where I could configure a port address for communicating with its
> SQL instance.
> Can someone provide me with information about what to configure in SQL
> Server Configuration Manager (and probably in Backup Exec - Symantec did not
> answer until now) to avoid the error messages?
> Thanx in advance,
> Tim
By default SQLExpress will not have remote connections enabled. If you are
using a database on the same server then you should not need to enabled
TCP/IP.
Have you checked these instances of SQL Server are running using the service
applet or typing NET START at a command prompt?
In the Network Protocols branch under SQL Server Configuration Manager, is
the protocol Enabled? If you double click the tcp/ip entry that you will get
the IP and port settings in the properties dialog.
John
|||Hi John,
thanks for input.

> In the Network Protocols branch under SQL Server Configuration Manager, is
> the protocol Enabled?
Which protocol? I tried them all, the error no. 3 remained.

> If you double click the tcp/ip entry that you will get
> the IP and port settings in the properties dialog.
Yes, but I don't no, wether these IP settings are the right ones for Backup
Exec, I don't know, what exactly it is what Windows is complaining about.
Finally I uninstalled BE and SQL Server and reinstalled it, but without
success.
You stated, that TCP is not needed if everything is running on one server.
So I think I'm going to ignore the message since everything seems to work.
Thanks again.
|||Hi Tim
"Tim Meltzer" wrote:

> Hi John,
> thanks for input.
>
> Which protocol? I tried them all, the error no. 3 remained.
>
> Yes, but I don't no, wether these IP settings are the right ones for Backup
> Exec, I don't know, what exactly it is what Windows is complaining about.
> Finally I uninstalled BE and SQL Server and reinstalled it, but without
> success.
> You stated, that TCP is not needed if everything is running on one server.
> So I think I'm going to ignore the message since everything seems to work.
> Thanks again.
It is not clear where exactly where the error message is being displayed! Is
this in Backup exec, SQL Server error log or the Windows Event log?
If after installing Backup Exec again what protocols are enabled?
John

How to configure ports in SQL server configuration manager

Hi,
unfortunately I mixed up the ip settings in SQL server configuration manager
(I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
have an event in the application protocol (3), it says that configuration fo
r
SQL instances "bkupexec" and "sqlexpress" are invalid.
I tried 100 different settings in SQL configuratin manager, but the events
are remaining. I cannot find out to configure this. Backup Exce for example
has nothing where I could configure a port address for communicating with it
s
SQL instance.
Can someone provide me with information about what to configure in SQL
Server Configuration Manager (and probably in Backup Exec - Symantec did not
answer until now) to avoid the error messages?
Thanx in advance,
TimHi
"Tim Meltzer" wrote:

> Hi,
> unfortunately I mixed up the ip settings in SQL server configuration manag
er
> (I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
> have an event in the application protocol (3), it says that configuration
for
> SQL instances "bkupexec" and "sqlexpress" are invalid.
> I tried 100 different settings in SQL configuratin manager, but the events
> are remaining. I cannot find out to configure this. Backup Exce for exampl
e
> has nothing where I could configure a port address for communicating with
its
> SQL instance.
> Can someone provide me with information about what to configure in SQL
> Server Configuration Manager (and probably in Backup Exec - Symantec did n
ot
> answer until now) to avoid the error messages?
> Thanx in advance,
> Tim
By default SQLExpress will not have remote connections enabled. If you are
using a database on the same server then you should not need to enabled
TCP/IP.
Have you checked these instances of SQL Server are running using the service
applet or typing NET START at a command prompt?
In the Network Protocols branch under SQL Server Configuration Manager, is
the protocol Enabled? If you double click the tcp/ip entry that you will get
the IP and port settings in the properties dialog.
John|||Hi John,
thanks for input.

> In the Network Protocols branch under SQL Server Configuration Manager, is
> the protocol Enabled?
Which protocol? I tried them all, the error no. 3 remained.

> If you double click the tcp/ip entry that you will get
> the IP and port settings in the properties dialog.
Yes, but I don't no, wether these IP settings are the right ones for Backup
Exec, I don't know, what exactly it is what Windows is complaining about.
Finally I uninstalled BE and SQL Server and reinstalled it, but without
success.
You stated, that TCP is not needed if everything is running on one server.
So I think I'm going to ignore the message since everything seems to work.
Thanks again.|||Hi Tim
"Tim Meltzer" wrote:

> Hi John,
> thanks for input.
>
> Which protocol? I tried them all, the error no. 3 remained.
>
> Yes, but I don't no, wether these IP settings are the right ones for Backu
p
> Exec, I don't know, what exactly it is what Windows is complaining about.
> Finally I uninstalled BE and SQL Server and reinstalled it, but without
> success.
> You stated, that TCP is not needed if everything is running on one server.
> So I think I'm going to ignore the message since everything seems to work.
> Thanks again.
It is not clear where exactly where the error message is being displayed! Is
this in Backup exec, SQL Server error log or the Windows Event log?
If after installing Backup Exec again what protocols are enabled?
John

How to configure ports in SQL server configuration manager

Hi,
unfortunately I mixed up the ip settings in SQL server configuration manager
(I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
have an event in the application protocol (3), it says that configuration for
SQL instances "bkupexec" and "sqlexpress" are invalid.
I tried 100 different settings in SQL configuratin manager, but the events
are remaining. I cannot find out to configure this. Backup Exce for example
has nothing where I could configure a port address for communicating with its
SQL instance.
Can someone provide me with information about what to configure in SQL
Server Configuration Manager (and probably in Backup Exec - Symantec did not
answer until now) to avoid the error messages?
Thanx in advance,
TimHi
"Tim Meltzer" wrote:
> Hi,
> unfortunately I mixed up the ip settings in SQL server configuration manager
> (I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
> have an event in the application protocol (3), it says that configuration for
> SQL instances "bkupexec" and "sqlexpress" are invalid.
> I tried 100 different settings in SQL configuratin manager, but the events
> are remaining. I cannot find out to configure this. Backup Exce for example
> has nothing where I could configure a port address for communicating with its
> SQL instance.
> Can someone provide me with information about what to configure in SQL
> Server Configuration Manager (and probably in Backup Exec - Symantec did not
> answer until now) to avoid the error messages?
> Thanx in advance,
> Tim
By default SQLExpress will not have remote connections enabled. If you are
using a database on the same server then you should not need to enabled
TCP/IP.
Have you checked these instances of SQL Server are running using the service
applet or typing NET START at a command prompt?
In the Network Protocols branch under SQL Server Configuration Manager, is
the protocol Enabled? If you double click the tcp/ip entry that you will get
the IP and port settings in the properties dialog.
John|||Hi John,
thanks for input.
> In the Network Protocols branch under SQL Server Configuration Manager, is
> the protocol Enabled?
Which protocol? I tried them all, the error no. 3 remained.
> If you double click the tcp/ip entry that you will get
> the IP and port settings in the properties dialog.
Yes, but I don't no, wether these IP settings are the right ones for Backup
Exec, I don't know, what exactly it is what Windows is complaining about.
Finally I uninstalled BE and SQL Server and reinstalled it, but without
success.
You stated, that TCP is not needed if everything is running on one server.
So I think I'm going to ignore the message since everything seems to work.
Thanks again.|||Hi Tim
"Tim Meltzer" wrote:
> Hi John,
> thanks for input.
> > In the Network Protocols branch under SQL Server Configuration Manager, is
> > the protocol Enabled?
> Which protocol? I tried them all, the error no. 3 remained.
> > If you double click the tcp/ip entry that you will get
> > the IP and port settings in the properties dialog.
> Yes, but I don't no, wether these IP settings are the right ones for Backup
> Exec, I don't know, what exactly it is what Windows is complaining about.
> Finally I uninstalled BE and SQL Server and reinstalled it, but without
> success.
> You stated, that TCP is not needed if everything is running on one server.
> So I think I'm going to ignore the message since everything seems to work.
> Thanks again.
It is not clear where exactly where the error message is being displayed! Is
this in Backup exec, SQL Server error log or the Windows Event log?
If after installing Backup Exec again what protocols are enabled?
John