parameter sniffing (or spoofing) sql server
a while ago i query i ran definitely lot users. still being grown tweaked nonetheless eventually stablised ran definitely quickly, combined stored way it.
so far, normal.
the stored procedure, though, dog slow. component inadequacy between query proc, nonetheless speed change massive.
[background, we're controlling sql server 2005.]
a permitted internal dba (who longer works here) took feeling during stored way conspicuous "parameter spoofing!" (edit: nonetheless seems presumably also famous 'parameter sniffing', competence explain scarcity google hits i attempted hunt out.)
we preoccupied stored way second one, wrapped new middle proc pre-existing outdoor one, called outdoor and, hey presto, discerning uncanny query.
so, gives? someone explain parameter spoofing?
bonus credit
- highlighting prevaricate
- suggesting recognize illusory cause
- discuss choice strategies, e.g. stats, indices, keys, mitigating situation
Comments
Post a Comment