In SQL Server, what are the typical symptoms of parameter sniffing? There is a wealth of information on the DBA.SE about what parameter sniffing is and how it relates to individual query performance circumstances. I was hoping that someone could provide some sort of canonical answer as to what the symptoms of parameter sniffing are. So that's the question:


  What are the typical symptoms of parameter sniffing that would lead to its diagnosis as a potential culprit in performance?
It's commonly a potential cause when a stored procedure takes wildly different times to complete with different parameters.

Or when a stored procedure is seen taking a less than brilliant approach to getting data with certain parameters.

These would indicate to me that SQL Server had based it's query plan on the first parameters it had seen, but that these parameters weren't really indicative for all the possible parameter values.