Home/ Questions/Q 6973623
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T17:07:55+00:00

Using sql server 2008, I have a simple stored procedure, the contents of which

  • 0

Using sql server 2008, I have a simple stored procedure, the contents of which are

DELETE FROM [ABC].[dbo].[LookUpPermissions] 
WHERE Code = @Code

In a recent code review, the DBA said I should “add parameter sniffing” which I believe means I should account for parameter sniffing. I’ve never done this in the past and I am not having any performance issues with the query so I would think it is unnecessary.

While I presume the answer may be user preference, would it be best practice to account for parameter sniffing? Is it necessary if the stored procedure is called on a small dataset, used infrequently and is having no performance issues?

edit
Is this only applicable to parameters used in a WHERE clause, or for example, would you possibly need to account for all parameters in an INSERT statement?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    A simple search for a single value like this shouldn’t be vulnerable to parameter sniffing. It’s more of a concern when the parameters passed in result in widely different results and the optimal execution plan varies from the one that has been previously produced.

    As an example, think of a query that looks for rows where a date column is between a @start_date and an @end_date. Calling the procedure with a date range of 2 days may produce/cache an execution plan that is not optimal for a date range of 1 year.

    • 0