The only explanation I can find is that the server seems to do a rtrim by default when comparing strings. Anyone can confirm this?

The d is ignored also :

select ascii('ad')

Looks like it returns the ascii of the first character only.

What's procedural about this???

CREATE FUNCTION dbo.ReplaceSpecialCharacter2000_2( @ValueToAlter varchar(2000))

RETURNS varchar(2000)

AS

BEGIN

SELECT @ValueToAlter = REPLACE( @ValueToAlter, Search, Replacement) FROM dbo.SpecialCharacters2

RETURN ( @ValueToAlter )

END

GO

And as I said it's easier to maintain .

I was testing for performance.

Have closer look at the call :

Select dbo.fnName (REPLICATE( 'f''gr"7 df@@8j\', 130))

I can't find squat on this behavior. The only stuff I find is about DTS.

Indexing strategy is far more complexe than just putting indexes. Maintaining them also has a cost and it can be pretty high.

I'm lineant... 100$/hour is fine for the trial period .

Probabely not impossible to do but it would be considered a worst practice. What action do you need to perform in that webservice that can't be handled on the...

HTH.

Make sure you understand the part about the order by in the exemple.. or this is gonna come byte you in the ass

What the hell kind of application was that??? I have one like that here and it's not pretty .

Alright... start a new thread for the next question so that others may benefit from the answer.

Select * from dbo.MyTable where MyField like '%''%'

Ok I defenitly signed the papers, where do I send them now ?