We have about 40 DB's blackening 40 web sites running on a single
SQL2k/Win2003 an A/P cluster. When I roll the cluster from one node to the
next I'm wondering exactly what sort of outage our clients would see. Since
the entire cluster rolls in under a minute would there just be a delay on
the web sites with data requests in response from the web/ODBC side or would
there be an ODBC failure. Also, with regards to active web sessions, would
clients mid transaction on the web pages need to restart their transaction
or would there be a short wait during the SQL roll and then they could
proceed with the transaction (or would they need to start all over again).
I guess I'm wondering if I need to add the 1 minute of roll time into our
annual downtime calculation if the clients see an application
failure/unavailability.
On the roll all client connections are lost and must be restarted. As for
what exactly happens, well that depends on the application. If the rows are
returned locally or if they are stored on the web server. And at what stage
in the process each client was in.
Bottom line, in most cases they either hit F5 (refresh) or never notice.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Mike B." <Autobahn97@.hotmail.com> wrote in message
news:eS8jOB3XEHA.3596@.tk2msftngp13.phx.gbl...
> We have about 40 DB's blackening 40 web sites running on a single
> SQL2k/Win2003 an A/P cluster. When I roll the cluster from one node to
the
> next I'm wondering exactly what sort of outage our clients would see.
Since
> the entire cluster rolls in under a minute would there just be a delay on
> the web sites with data requests in response from the web/ODBC side or
would
> there be an ODBC failure. Also, with regards to active web sessions,
would
> clients mid transaction on the web pages need to restart their transaction
> or would there be a short wait during the SQL roll and then they could
> proceed with the transaction (or would they need to start all over again).
> I guess I'm wondering if I need to add the 1 minute of roll time into our
> annual downtime calculation if the clients see an application
> failure/unavailability.
>
|||What the clients see or how it affects their transactions depends solely on
how the client app was written. It must be cluster aware. By that I mean
it must be able to detect a connection failure and reconnect. It must also
be able to resubmit the current transaction as it will be rolled back on the
server side when the cluster comes back up.
Andrew J. Kelly SQL MVP
"Mike B." <Autobahn97@.hotmail.com> wrote in message
news:eS8jOB3XEHA.3596@.tk2msftngp13.phx.gbl...
> We have about 40 DB's blackening 40 web sites running on a single
> SQL2k/Win2003 an A/P cluster. When I roll the cluster from one node to
the
> next I'm wondering exactly what sort of outage our clients would see.
Since
> the entire cluster rolls in under a minute would there just be a delay on
> the web sites with data requests in response from the web/ODBC side or
would
> there be an ODBC failure. Also, with regards to active web sessions,
would
> clients mid transaction on the web pages need to restart their transaction
> or would there be a short wait during the SQL roll and then they could
> proceed with the transaction (or would they need to start all over again).
> I guess I'm wondering if I need to add the 1 minute of roll time into our
> annual downtime calculation if the clients see an application
> failure/unavailability.
>
|||A cluster host transition is exactly like a SQL server stop-start. All
transactions are rolled forward or back at startup. The server is down
during the transition. The client application will see a connection timeout
or a query timeout or a broken connection. Whether the application traps
that or displays that to the end-user depends on the skill of the programmer
who wrote it.
Short answer, a cluster transition is downtime.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Mike B." <Autobahn97@.hotmail.com> wrote in message
news:eS8jOB3XEHA.3596@.tk2msftngp13.phx.gbl...
> We have about 40 DB's blackening 40 web sites running on a single
> SQL2k/Win2003 an A/P cluster. When I roll the cluster from one node to
the
> next I'm wondering exactly what sort of outage our clients would see.
Since
> the entire cluster rolls in under a minute would there just be a delay on
> the web sites with data requests in response from the web/ODBC side or
would
> there be an ODBC failure. Also, with regards to active web sessions,
would
> clients mid transaction on the web pages need to restart their transaction
> or would there be a short wait during the SQL roll and then they could
> proceed with the transaction (or would they need to start all over again).
> I guess I'm wondering if I need to add the 1 minute of roll time into our
> annual downtime calculation if the clients see an application
> failure/unavailability.
>
|||During the failover process, any active connections are broken. For Web browser users, a simple refresh of the Web page should create a new database connection. In a more traditional client/server application, or
one that relies heavily on a middle tier, application designers may want to consider checking to see whether the connection exists, and if not, reconnect. Therefore, whatever the user was working on when the server
went down may not be completed, unless the transaction completes before the server goes down or the transaction is handled within the application.
For more information, see the Knowledge Base article "Q273673 - Virtual Server Client Connections Must be Controlled by Clients" at:
http://support.microsoft.com/?kbid=273673
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
