I'm curious. Is there any way to prevent SQL query execution plans from being cached for an entire connection's duration?
Can I run a command that basically says, "use OPTION(RECOMPILE) for all subsequent commands until I tell you to stop doing so?"
I'm acutely aware of all the performance trade-offs here, and I know this is not a step to be taken lightly. However, I'm in a unique situation where this behavior may be advantageous.
UPDATE: I found trace flag 253, but cannot find official mention of what exactly it does: http://stackoverflow.com/questions/2596587/what-does-sql-server-trace-flag-253-do