Best practices for connection retry..SQL Azure

[Scott Fairbairn]

I'm interested in utilizing BTToolkit against a SQL Azure database.

SQL Azure -based applications have to handle the condition where Azure
moves around load and connections unexpectedly timeout thus requiring
exception handling and retry logic relating to the SqlConnection in
question.

Microsoft has recently posted this framework and examples as a best-
practices method to handle these conditions...

http://blogs.msdn.com/b/appfabriccat/archive/2010/10/28/best-practices-for-handling-transient-conditions-in-sql-azure-client-applications.aspx

What would be the best way to utilize this framework within the
context of BLToolkit's API? Could you provide some potential
examples? I'm uncertain if the connection object is accessible and
can be wrapped properly while still leveraging some of the great
capabilities of BLToolkit, including the latest LINQ syntax.

Also, is there any existing connection retry logic already within
BLToolkit to handle connection loss when talking to the servers? This
is a common condition both in cloud computing and in clustered
failover environments, and would be a big bonus to the toolkit if
properly implemented.

Essentially, you could just plug it in, and the rest is taken care of
- interestingly, NHibernate says with SQL Azure that "it just works",
but they fail to mention that they are doing nothing to manage
connection retries, so clearly, it couldn't just work for very long.

Any feedback would be greatly appreciated.

[stepa...@gmail.com]

You can find my sources of AzureSqlDataProvider on github. Also it's available over NuGet. 

Please, see how to install and configure it here.

пятница, 3 декабря 2010 г., 5:55:39 UTC+4 пользователь Scott Fairbairn написал: