This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I am developing an enterprise application which will be using SqlAzure. I have been reading up on SqlAzure and basically, connections can be dropped anytime. The recommendation is to use a retry logic for certain errors. Here is an article discussing this approach: http://social.technet.microsoft.com/wiki/contents/articles/retry-logic-for-transient-failures-in-sql-azure.aspx Does LightSpeed already have this type of retry logic baked in for SqlAzure? I have already implemented a custom RetryConnectionStrategy, but I don't know where to implement retry logic for a SaveChanges? Is there another xxxStrategy that I need to implement? Thanks Jeffrey |
|
|
Hello Jeffrey, No, we don't have retry logic baked in, so a RetryConnectionStrategy is the right way to go. There is no separate strategy class for implementing SaveChanges retry logic, but you can override UnitOfWork.SaveChanges(bool) and implement your retry logic there e.g.
|
|
|
Thanks for the advice Ivan Regards, Jeffrey |
|