I am very interested in a definitive answer here... In a shop like mine where they don't want any stored procs to be used at all, and where they believe that having an in-house DBA is a waste of money (I'm not even kidding), how does one make a convincing argument for stored procs? They are .NET developers who know a bit of SQL; I am a SQL developer and former DBA who was hired to do .NET. I can tell them all of the advantages of stored procs -- protection against SQL injection, greater speed if well-written, quicker deployment -- but I don't know enough about Entity Framework to be able to give them the down sides in a confident way when comparing Entity Framework (with direct mapping) to stored procs...