There are the following disadvantages of LINQ over Stored Procedures. LINQ query is compiled each and every time while stored procedures re-used the cached execution plan to execute. Hence, LINQ query takes more time in execution as compared to stored procedures. LINQ is not the good for writing complex queries as compared to stored procedures. LINQ is not a good way for bulk insert and update operations. Performance is degraded if you don’t write the LINQ query correctly. If you have done some changes in your query, you have to recompile it and redeploy its dll to the server.
There are the following differences between LINQ and Stored Procedures. Stored procedures are faster as compared to LINQ query since they have a predictable execution plan and can take the full advantage of SQL features. Hence, when a stored procedure is being executed next time, the database used the cached execution plan to execute that stored procedure. LINQ has full type checking at compile-time and IntelliSense support in Visual Studio as compared to stored procedure. This powerful feature helps you to avoid run-time errors. LINQ allows debugging through .NET debugger as compared to stored procedure. LINQ also supports various .NET … Click here to continue…..