I'd with with Noeld's solutions as they don't use a #temp table which would really not be a best pratice in this case.

Same here, the left join will have less work to do than the subquery... or at least do it in a more efficient way.

Basically you need to have the same set options on the table and on the view... While I can't really help you on that because I never investigated this...

strDisplayQuery="select DocumentID,Title,ReleaseDate,Disable from tblDocument where DocumentTypeCode = " & rv & " Order by ReleaseDate DESC"

I had the exact same problem yesterday... The hd only had 2 mb left of space. Moved a 4 gig db to its own drive and I never had...

Please don't cross post. Your question has been answered here :

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

Just another thaught on this. If this search is occuring often and considering the pretty great number of rows, wouldn't it be better just to create a new column...

Most of us wouldn't ear a living without it... Har dnot too love it just a little bit

I thaught that there might have been some "forbidden" characters in the string but obviously not... I can't help you then.

Good luck.

What are the names of the missing columns?

This wouldn't work here because it's 6 tables parametered search report.

thanx, PhilPacha. Looks like I wasn't complettly off target .

Can you tell us why you need to have a column point to 2 different foreign keys? I cannot imagine a situation where I would have to do this...

Select * from objsql where exists (Select * from dbo.SysObjects) != 0

Serveur : Msg 170, Niveau 15, État 1, Ligne 1

Ligne 1 : syntaxe incorrecte vers '!'.

you can't have !=...

I already saw that once. I was using a memo field. This bug occured when that memo field suddenly grew from only a few bytes to a few...