Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server connection rejections and client application management Expand / Collapse
Author
Message
Posted Thursday, May 28, 2009 12:12 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, July 2, 2009 2:39 AM
Points: 3, Visits: 19
Scenario:

1. Connect to a remote SQL server from a client SQLWB window and run SP_WHO2
2. Consider, the SQL Server's network port is being unplugged
(or SQL server is no longer available due to being shutdown or a network problem/Disconnect the SQL server machine’s Ethernet port)
3. Wait for 5 min
4. Reconnect the SQL Server's network port
(SQL server is restarted or a network problem has been resolved/Connect the Ethernet port back)
5. Run the same sql statement SP_WHO2(in the same window created in step 1) without doing any changes to the connection or to the window itself
6. It will get you the connection as closed or with some error

Will this be a case of,

Fatal error ?
The client closed the connection?
The server itself killed it?

Our requirement is to develop a program:

To keep track of the rejections occurred by the fatal error
To monitor connections which were rejected by SQL Server and the cause behind it
The best way to detect when SQL server is no longer available due to being shutdown or a network problem.

Also need the following:

What are the scenarios for fatal error?
What are the instances were a connection is killed by a Server without the knowledge of the client?(It’s irrespective of the type of error responsible for this)
In case of network downtime or no network, who is taking care of connection status? (Client or Server ?)

Post #724819
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse