But if you keep at it you might lose it in the first few months of answering questions here... like I did.

No offence but this title is a little bit harder than that to lose .

Sql server caches the plan based on the first set of input parameters you send.  If you sent an unlikely set of parameters, then the server may have saved an optimized...

NP, I had plenty of oversights like this one in the past... too bad you had to waste a ticket for this one.

Dude it's the same code.  I've not tested this but I'm pretty sure it will work :

Declare @NSQL AS NVarchar(4000)

DECLARE @Return AS INT

set @NSQL =...

Unless available...  You'd have to audit this information daily / hourly or howver-ly with a job so you can be sure to catch them all.  A snapshot every 3 months...

ALTER TABLE #TMPTest ADD [NewCol] INT  >> or change the colname altogether.

I'll submitt to you that the real column name is most likely a reserved keyqord...

That should give you an idea of where to start with sp_execsql :

  IF @NewLogSize IS NOT NULL

   BEGIN

    SET @SizeTooSmall = 0

    SET @NSQL = 'SELECT @SizeTooSmall = COUNT(*) FROM ['...

It works for remote queries too?

Do you have restrictions such has you must have the linked server setup?

I think you'll have to do a workaround and run this with some sort of script that gets the return value (using openrowset or openquery), then selects that return value...

If the output needs to change for all ids, but that all ids are repeated quite often you may have an option (this is assuming that the function really takes...

There's much more to parameter sniffing than that.

This can also be related to your problem.

http://www.sqlservercentral.com/columnists/bkelley/procedurecache.asp

Try making a copy of the input parameters to local variables and then using those...

If those are not around, then how come the server be up and running??  Are you sure that the server is running?  Are you sure you checked in the Master...

Search parameter sniffing on this site.  There must be 100 threads talking about this.  If you still have questions, I'll gladly adress them after you gave this a try a...

Was the problem in a newly restored database?

In a newly installed database?

Found any errors in the scripts that were ran?

Or maybe some scripts that were not run?