Udostępnij za pośrednictwem


Best Practices for Handling Transient Conditions in SQL Azure Client Applications

This post has been moved to a new location. Please follow the link below. Thank you.

https://windowsazurecat.com/2010/10/best-practices-for-handling-transient-conditions-in-sql-azure-client-applications/

Comments

  • Anonymous
    November 30, 2010
    The comment has been removed
  • Anonymous
    December 09, 2010
    We are collaborating with the Entity Framework team to be able to provide a consistent story here. We will publish our recommendations in due course.
  • Anonymous
    December 27, 2010
    The comment has been removed
  • Anonymous
    January 04, 2011
    Peter, thank you for reaching out to us.Please note that the test project included into the source code distributed on the MSDN Code Gallery is reserved for internal testing and prototyping purposes and should not ideally be used as implementation guidance. I recommend you to review the following post that specifically talks about retry scenarios with Entity Framework.blogs.msdn.com/.../sql-azure-and-entity-framework-connection-fault-handling.aspx
  • Anonymous
    January 20, 2011
    As shown previously it isn’t hard to run Workflow Services on Windows Azure. In fact all we need to do
  • Anonymous
    March 03, 2011
    There is a dependency on Microsoft.ServiceBus but I don't have that dll in my system, that I know of. It does not show in the references dialog and is not in the Windows Azure 1.3 SDK folders. I searched Microsoft Download and it returned nothing. Where can I get this dll? Or where on my system might I find it?
  • Anonymous
    March 03, 2011
    Never mind, I found it. It is part of the AppFabric SDK which I did not have installed. In case anyone is looking for it I got it from:www.microsoft.com/.../details.aspx
  • Anonymous
    May 24, 2011
    When will MS Patterns & Practices Data Access Block include this type of logic and config?Thanks
  • Anonymous
    June 08, 2011
    Hi Niall,It's a perfectly valid question for the P&P team. We already provided them with all the code artifacts and asked to integrate the retry framework into the DAB. If you look at the work we have done with the EntLib's DAB, you will see that it's not too difficult to implement such integration yourself.appfabriccat.com/.../enterprise-library-on-windows-azure-key-learnings-from-customer-projectValery
  • Anonymous
    June 17, 2011
    Niall, perfect timing!The EntLib team is currently in the exploration phase for the Windows Azure Integration Pack for Enterprise Library 5.0. Please suggest this as a story on our uservoice site. Other users will be able to vote on this and we'll take that into consideration when finalizing our product backlog.Thanks,GrigoriEnterprise Library producer
  • Anonymous
    June 17, 2011
    Here's the uservoice link: entlib.uservoice.com/.../101257-azure-integration-pack
  • Anonymous
    June 22, 2011
    The comment has been removed
  • Anonymous
    June 23, 2011
    The comment has been removed
  • Anonymous
    June 26, 2011
    Wow, that was fast!  Working perfectly for me now.
  • Anonymous
    August 07, 2011
    I tried this RetryPolicy because I want a robust application.I have the following code:int MaxRetry = 5;int DelayMS = 100;policy = new RetryPolicy<SqlAzureTransientErrorDetectionStrategy>(MaxRetry, TimeSpan.FromMilliseconds(DelayMS));Type = policy.ExecuteAction<string>(() => context.properties.First(p => p.Name == "not_exist_type_id").Value);but it sometiomes throws exception:"Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding."  The RetryPolicy is not working if the connection times out?Best regards,Tom
  • Anonymous
    August 08, 2011
    The comment has been removed
  • Anonymous
    August 14, 2011
    I cannot find examples for how to use your framework for retrying Azure storage operations.  Any hints?
  • Anonymous
    August 15, 2011
    Hi oliverbock,We have a plenty of real-world examples of how to use the framework with Windows Azure queues and blobs in order to make storage operations more resilient to transient faults. Specifically, please review the following post and download the sample code.windowsazurecat.com/.../implementing-storage-abstraction-layer-to-support-very-large-messages-in-windows-azure-queues