Entity Framework cached query plan performance degrades with different parameters?

There's a way to remove a single plan from SQL Server's cache. It's explained in detail here: sqlblog.com/blogs/kalen_delaney/archive/....

There's a way to remove a single plan from SQL Server's cache. It's explained in detail here: sqlblog.com/blogs/kalen_delaney/archive/... Also, you can create a Stored Procedure, and map it with Entity Framework instead of using LINQ2Entities, and in this way make spcific changes to the SQL syntax, and make sure it's always the same.

Svarog, Thank you very much, the blog really hits the nail (it issues the exact same problem I have) and provided me: a) a "more elegant" workaround I can use inmediately in development: flushing only the problematic database proc (not the entire server cache) cache with: db. ExecuteStoreCommand("DECLARE @myDb AS INT = DB_ID(); DBCC FLUSHPROCINDB(@myDb)"); b) a workaround for production environment, since sp_create_plan_guide is not available for SQL EXPRESS. I'm not sure this is a problem in Enterprise, but I'm begining to think this will have to do in production.

Thank you very much! – Jerónimo Vargas Nov 1 at 17:42.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.