Hi, I have several parameters that I need to pass to stored procedure but sometimes some of them might be null. For example I might pass @.Path, @.Status, @.Role etc. depending on the user. Now I wonder if I should use dynamic Where clause or should I use some kind of switch, maybe case and hardcode my where clause. I first created several stored procedures like Documents_GetByRole, Documents_GetByRoleByStatus ... and now I want to combine them into one SP. Which approach is better. Thanks for your help.dynamic where clauses would eliminate most of the benefits of the stored procedure.
For every ad-hoc query that's executed, a new execution plan and compiliation takes place. Furthermore, your ram goes up.
A lot of databases will slow down with usage due to this. Therefore, hardcoding your where clauses is best. (like field = @.value)
No comments:
Post a Comment