Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I currently use SQL Azure and Entity SQL in my application.
e.g.
Entities model = new Entities();
db_Item item = model.db_Item.First();
Now I want to use the Transient Fault Handling out of the Enterprise Library but there are no examples or solutions that I can find that would allow me to do something like override the Entities class, so I don’t have to update my code in hundreds of places.
Could someone please provide more information on how this could be done?
Going through what I have so far.
The Entity Framework does not provide access to the connection open and section where the SQL is sent to the server, hence it is currently impossibile to provide retry logic around this area.
The EF team are aware of this shortfall and are planning on actually integrating retry logic into EF for possibily version 6.
As per Case #3 of [1] you can send a SQL command to the database on the OnContextCreated. This however means for EVERY single DB call you make to the DB, you will have to make 2. I wouldn’t recommend this in hardly any situation unless you don’t care about performance.
The only viable option so far is implementing retry logic in the form of the Enterprise Library Transient Fault Handling Application Block [2] around every call you make to the database. In existing applications this is extremely tedious.
When I get time I am looking further into the source code of EF to see if anything further can be done, while we wait for EF 6. I would keep an eye on [3]
Some hope, it is currently under review by the EF team. [4]
Update: 2013-11-14
Just thought I would update this post to let everyone know that EF6 has been released and supports connection resiliency out of the box. https://www.nuget.org/packages/EntityFramework/
No need for workarounds any more.
Update: 2013-03-23
EF 6 Alpha 3 released with Connection Resiliency – http://entityframework.codeplex.com/wikipage?title=Connection%20Resiliency%20Spec
Update: 2012-11-04
The EF team have officially announced it is planned for EF 6. [4]
[1] http://blogs.msdn.com/b/appfabriccat/archive/2010/12/11/sql-azure-and-entity-framework-connection-fault-handling.aspx
[2] http://msdn.microsoft.com/en-us/library/hh680934(v=pandp.50).aspx
[3] http://entityframework.codeplex.com/wikipage?title=Roadmap
[4] http://data.uservoice.com/forums/72025-entity-framework-feature-suggestions/suggestions/2426525-automatically-perform-retry-logic-for-sql-azure