dbo.SpName

then in the inputparameter property, you enter all the needed parameters.

I might have to change my way of thinking on those questions... but still when someone asks how to do something in dynamic sql, I'll ALWAYS try to make them...

There's still a faster way . Cya thuesday.

Select case when Surname like 'A%' then Surname + ', ' + FirstName

when FirstName like 'A%' then FirstName + ', ' + Surname

end

from....

BTW this is something that would be faster...

I'll make one for you Monday (can't test anything on this pc).

Do you need to know how many there are, or just find if there are upper case letters. ...

Nice plan... but it still requires changing every single proc. I think it would be simpler to just send the calling spid .

Good point... I guess he'll have to tell me that for me to give that answer .

Ya index tuning should be a daily task... reindex all the tables that meet a set treshold so that you don't have to do 'em all at the same time.

Dynamic Search Conditions in T-SQL

It's already been said that it's possible, but this task should be done at the client.

Please do not cross-post.

Finish the thread here :

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=216775

Please do not cross-post.

Finish the thread here :

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=216775

Let's put it that way... it's always cached untill it is dropped from the cache by the server, or when you recompile the sp (or change the definition). Also...

NP. Almost every string manipulation is easier at the client side.

Doh!! Forgot the easy fix : DBCC FREEPROCCACHE

the server was using a cached copy on some of those calls.