Would like to see the # of post of the girls vs boys... then we could really see if that means something .

No chance... not gonna risk locking up the temp systables for such a simple query... and do it a 2 steps too when only one is needed.

You started it .

You can't do select * from @TableName. This would be dynamic sql, or requires a table variable.

The Curse and Blessings of Dynamic SQL

"And when they show their claws I run like a scalded dog."

You can run but you can't hide, resistance is futile.

That's not it. The avatar is its tranformer logo, the rectangles is another logo (linked with post count/member status??).

Don't know but it's gonna be in my book someday .

I'm not the kind to cross the line (too often). I know when to stop but that guy had it coming.

P.S. "prerogative to vacillate between bloodthirsty and peaceloving"

That...

You can always transfer the write part to a job.

Raise an alert in the proc.

The alert makes the job start.

Shouldn't have any security issue.

I won't agree on this one because that would be redundant . Thanx for the info.

Hey how come I have question marks under my name while you have a nice(r) logo??

Don't know about the severity level... good point though. Maybe this is not a task to be handled in a proc.

"operation finishes very fast and you leave the complexity to the outer query to do the order by and Presentation stuff."

As it should be...

And I'll try to type slower but...

I have to disagree on this one... a query still is a query even with full-text :

Select * from dbo.Problemes where contains (*, 'tester*')

PkProbleme TitreProbleme ...

He got 20 sweet answers along with 5 clear warnings that he was over the line. Sometimes you have to drive the point home, harder.

I know you live in...