I can't remember the name of a failure in query design

I'm on SQL Server

It's about parameter values being attached to a slow query plan where if you reset the query plan cache for that query with a different set of parameters it speeds it up

The name of this is on the tip of my tongue ...

parameter .. sniffing?

@jcolebrand I don't know if I would outright call parameter sniffing a failure in query design, but the way you've described the issue, parameter sniffing does seem to be what you are asking about.

@AndriyM Well you know how you can run a query with a bad parameter and it blows up the cache but then if you run it with a different parameter suddenly 99% of the queries are perfectly happy?

I can't remember the name of that syndrome, and I think that parameter sniffing is the "root cause" but I swear there's a better name

There's also this thing called forced parametrisation, but I think it's different from what you described

Yeah that doesn't sound the same

idk, it's just documentation to guide devs not doing something incredibly stupid

They either will or won't live up to the opportunity, who knows

Parameter masking is one antidote.

hi there, any way I could set up a mongoDB server for free? No Atlas but something I could set up with configuration files.

@jcolebrand It's often called the Parameter Sensitivity Problem

docs.microsoft.com/en-us/azure/azure-sql/…

Q & A dba.stackexchange.com/a/132816

Conor C: docs.microsoft.com/en-us/archive/blogs/conor_cunningham_msft/…

> parameter sensitive problem (PSP)

Took me a while to find that one because Microsoft broke all the msdn blog links

DBA will be ten years old in January

> Private beta: 2011-Jan-03 Public beta: 2011-Jan-10

> Graduation: 2011-Aug-16

Nice