It is on a cluster, can you elaborate on the steps I would need to take?

Oh i see gotcha thanks Gail

If I put it at the top of statement, it says 'completed' but when I go back in and look at the proc, the isolation level part I just added...

Thanks Gail

Thanks for answering and yes they know the risks Gail.

And hey, not my call...they want it on every one of these procs.

Guess I was just wondering if putting it as...

THANKS !!! Everyone...!

That did the trick

Good karma to you all.

Thanks GSquared.

Here's the proc that calls the two functions:

USE [FL16_QA]

GO

/****** Object: StoredProcedure [dbo].[_TPX_NameSearch_SEL] Script Date: 02/19/2009 13:55:08 ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

ALTER PROCEDURE [dbo].[_TPX_NameSearch_SEL]

@fullname varchar(100)

,@minPercentage...

much thanks for the comments..we are using if's and they seem to preform okay...

Why do I have a feeling the case statments would have worked better..or..some other form of case..?...

Thanks Gail,

We went to the link you provided and re-wrote the proc.

It seems to be working well.

Thanks again.

Here's the defiition.

The reason for dynamic sql, the front end has various fields the user may/may not enter and we don't know which they'll send.

USE [LoggerSource]

GO

/****** Object: Table [dbo].[Logger2]...

Thanks Carolyn,

I got a syntax error and moved the "+" outside of the single quote on @RequestId and Convert(Unique......

Now I'm gettting the following error: Operand type clash:...

AAAhhhhh I seeee said the blind man.....thanks Greg!!!

I'd like to avoid using dynamic sql, so I'm open to any suggestions. There are 12 potential parameters in all.

I tried Greg's suggestion, but in my case,...

🙂

Thank you all VERY much for taking the time to help me. Good karma to all of you.

You know, after getting a little sleep..I think the overall theme here is...