Sounds more like it... From incomplete after 2 days to 14 secs... how many folds are we talking about here??

Yes there's a way but I don't see why you would want to do this in this case. I'm under the impression that you are trying to do some...

not without coding it yourself.

Actually my demo is meant to be used like this :

Select Col_id, Col1 from dbo.MyTable where

(MyField = @MyField or @MyField = 'All')

and

(MyField2 = @MyField2 or @MyField2...

Could you post the final script so that people that come across the same problem can see the working solution?

Assuming you have 300 000 records in each table

FROM

contact2, contact1

WHERE contact2.accountno = contact2.accountno

and contact2.accountno...

NP... hopefully someone else will be able to find you problem.

Good luck.

this is a complete guess ... but may it be that MORE 'middletier2_log' should be MOVE 'middletier2_log'

(I never did this so I might be completly off here)

I would check the execution plan of the function and check for scans and try to turn then into seeks... it's the most likely reason for your slowlyness.

can't answer for sure... but I'd assume time clock... since there's a column for the cpu cycles.

I haven't read all the procs but here's my rule of thumb :

If I have different select statements (the columns changes, or the joins change), then make difference sps...

I think you're better off making 3 columns : first, last and middle name and split that column into those 3, then you can join those however you want in...

yes that column is in milliseconds.

this update is gonna table a while... you have 500 000 keywords about 88 000 indexes. the udf will be called once for each index. This is gonna...

Totally agree here... It would be nice to see how many questions we have left to get points.