Steve,

Heh... this is one of the things on my upcoming wish list... it would be great to be able to control a lookup for posts that have <= X replies...

True... but I'd still try. And, it's not just grammer... using the correct words can mean the difference between someone thinking that...

Heh... stop watch or ...

DECLARE @StartTime DATETIME

SET @StartTime = GETDATE()

--...code to measure duration of goes here...

PRINT CONVERT(CHAR(12),GETDATE()-@StartTime,114) + ' Duration (hh:mi:ss:mmm)'

GilaMonster (12/3/2007)

Why would you say that?

I'd say B. Dates should be stored in datetime columns, not seperated out. There are a couple of good reasons

There are some quite...

Sergiy (12/1/2007)

Well, procedure is doing the same thing to the same object (or, better, "object").

If...

I still want to know why it's necessary to return a 42 million row result set... THAT's the performance problem... especially if ANY of the "dim" tables are actually, ugh,...

You can gain some very fine control over the "order" of what get's done by triggers... put all the code in the correct order in one trigger.

Heh... no... I can't... don't have 2k5...

From what I understand, Cross Apply has some performance limitations... I was looking...

And Vivian's good script lists the FreeSpace in Mega Bytes.

Heh... You weren't supposed to remove the TOP... thought you only wanted ten random names at a time... and I sure didn't know you had a list of over 20,000...

Can you post what some of the output looked like? Thanks.

Ummm... maybe you can do it using OPENDATASOURCE or OPENROWSET...

Can't be done using EXEC... temp table must already exist.

Why do it two different ways?... and have one crawl if the scalability increases?

Dunno about others... but I've not needed anything but T-SQL with occasional trips through xp_CmdShell to use some "DOS" functionality.