I still vote for the kick... simple reporting task best handled AT THE CLIENT.

Very nice solution anyhow if you want to waste cpu time on the server.

DITO .

That's always a good idea to type faster... but shouldn't DBAs always have a backup, just in case???

Check this out for more details on performance conversions :

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=215358&p=2

Maybe I'm not clear in my requests "... some sample data along with the needed results and..."

Can you concatenate this parameter in a varchar(8000) like this?

'1,3,5,86,234'

No but those are nice .

Please do not cross-post we monitor all boards.

Check my follow-up question here : http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=169&messageid=215614

Please post the actual ddl of the table, some sample data along with the needed results and we'll build the query for you.

It's the session that timed out (or something similar)... remember to copy your message somewhere if it takes a long time to write.

So true, thanx for the new performance tuning insigth .

Can you give out more details?

I just played with this... looks like we are both right about what is he fastest... just depends on the number of lines :

Declare @i as int

Declare @Maxi as...

I never tried this but I think it's possible :

Drop all the procs on the copied db. Then check out yesterday's articles on how to execute a result...

Can you make a backup of the db and restore it under a new name?