When using aggregate queries in the Entity Framework (or linq-to-sql) in conjunction with SQL Server Actually still using any stored procedures to gain performance?
Collected queries will be cached in the form of a parameter, so the performance should be equal to stored procedures. Is there a situation where the stored procedure will perform very well?
- Edit
In response to the Yakimik's answer given below, I did not mean that the compiled questions are similar to the stored procedures that I am trying to explain Is the spread still necessary if you have made all possible adaptations on the application side (in this case the compiled question). So I think I'm looking for reasons why a stored procedure would be better than the combination of questions with application-side optimization and parameters (which is a compiled question effectively).
> I am asking that one of the reasons is this, because there are many people who feel that the foundation laid out for different reasons (i.e.) is no longer necessary.
"Is there a situation where stored procedures will perform very well?"
Looking at the comparable piece of SQL with the parameter, either in EF or in a stored proc, they will perform equally well.
However, a DBA always provides an opportunity to customize a query based on its experience with DB Schema and its usage patterns. A stored procedure allows them to be easily used in the isolation of applications using it, while an ORM does not.
We have a very complex SQL Server DB that has many external systems running in it. The issue for us with EF is that the responsibility of SBU will be removed on DB, application developers will be responsible for using any ORM instead of DBA.
Comments
Post a Comment