468,115 Members | 2,122 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,115 developers. It's quick & easy.

ASP.Net connection to a failed over SQL Cluster

In an ASP.Net V2 application that has the connection string as

"Data Source=MySQLClusterInstance; Initial Catalog=myDB; User
ID=aUser; Password=aPassword; Persist Security Info=True;"

Then when the SQL cluster is failed over and is running on another
node the following error is displayed in the web page.

A transport-level error has occurred when sending the request to the
server. (provider: TCP Provider, error: 0 - An existing connection was
forcibly closed by the remote host.)

If the web page is closed and then reopened it works on the connection
to the failed over node.

What is required to change to allow the .Net application to work when
the SQL Cluster is failed over to another SQL Node?
Nov 19 '08 #1
2 3131
sqlserver clusters do not support seamless failover as its the connect logic
that handles the failover. your code should detect the lost connection,
reconnect and start the transaction over (all pending tranaction will have
been rolled back). if this is too hard to code, catch the error and render a
retry button.

-- bruce (sqlwork.com)
"Robin9876" wrote:
In an ASP.Net V2 application that has the connection string as

"Data Source=MySQLClusterInstance; Initial Catalog=myDB; User
ID=aUser; Password=aPassword; Persist Security Info=True;"

Then when the SQL cluster is failed over and is running on another
node the following error is displayed in the web page.

A transport-level error has occurred when sending the request to the
server. (provider: TCP Provider, error: 0 - An existing connection was
forcibly closed by the remote host.)

If the web page is closed and then reopened it works on the connection
to the failed over node.

What is required to change to allow the .Net application to work when
the SQL Cluster is failed over to another SQL Node?
Nov 19 '08 #2
Can you use DTC to handle the database transactions or does it require
ASP.Net code changes?

On 19 Nov, 16:26, bruce barker <brucebar...@discussions.microsoft.com>
wrote:
sqlserver clusters do not support seamless failover as its the connect logic
that handles the failover. your code should detect the lost connection,
reconnect and start the transaction over (all pending tranaction will have
been rolled back). if this is too hard to code, catch the error and render a
retry button.

-- bruce (sqlwork.com)

"Robin9876" wrote:
In an ASP.Net V2 application that has the connection string as
"Data Source=MySQLClusterInstance; Initial Catalog=myDB; User
ID=aUser; Password=aPassword; Persist Security Info=True;"
Then when the SQL cluster is failed over and is running on another
node the following error is displayed in the web page.
A transport-level error has occurred when sending the request to the
server. (provider: TCP Provider, error: 0 - An existing connection was
forcibly closed by the remote host.)
If the web page is closed and then reopened it works on the connection
to the failed over node.
What is required to change to allow the .Net application to work when
the SQL Cluster is failed over to another SQL Node?
Nov 20 '08 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Sergej Grickov | last post: by
2 posts views Thread by Rahul | last post: by
5 posts views Thread by russell.lane | last post: by
reply views Thread by kbrolin65 | last post: by
6 posts views Thread by Gibble | last post: by
3 posts views Thread by sck10 | last post: by
3 posts views Thread by didacticone | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.