Because "" is the quoted identifier, so that gets converted to a sysname (name of an object/column) which internally is nvarchar(128).

Did you try ''' comchar'',''dfdsd;'',''........'''??

Have you considered using...

just ran some more test inserting in a temp table

--17576 rows in 11 seconds

--456976 rows in 43 seconds

ran out of space in tempdb for the final pass (after almost 9...

Slim is an understatment here...

waiting for query and calling code before trying to solve this one.

This generates 11881376 rows in 71 seconds (without sorting) on a slow server

Select dtA.Frst + dtB.Sec + dtC.ThD + dtD.Fourth + dtE.Fifth As GenList FROM

(Select CHAR(PkNumber) as Frst from dbo.Numbers...

Try replacing " with ''.

Also read this :

Dynamic Search Conditions in T-SQL

The Curse and Blessings of Dynamic SQL

September 15, 2005 at 12:28 pm

#590292

I'll take a wild guess and go with "NS" = "notification services" as it is posted inder that forum .

I can't believe we all (almost) missed that one .

== is not gonna work with sql

if @var = null is also gonna fail most of the time.

First of all DBMS XML.

XML is nice and all but it's like a 1950 DB model. But that's just my opinion and I don't really know on what...

"select * from trans where date >= '05/01/2005'"

might be better to use a sp instead of dynamic sql too .

and to finish this game :

SET @ACCOUNTTIME = COALESCE(@ACCOUNTTIME,0)

Ya I'd check that first now that it is suggested .

I'd go with the auditing part. Good indexing should be this work pretty well.

I imagine that this is a pointer, as for refferences I'll let the other dbas take it as I have very little experience there.

wow... tried rebooting, reinstalling??