CONVERSELY... smaller fill factors also means SELECTs have to wade through more blank pages which will slow them down.  If the table is a static lookup table (one that rarely,...

Vladan!  Good to "see" you... Now that was funny!  Thanks for the laugh...

Nope, sorry... I'm afraid only the boys in Redmond know the answer to that one (Group By/Distinct time changes) although it does make one question the myth that clustered indexes...

You bet... thank you for the feedback...

Sorry I'm so late on this one (2 1/2 years aint too bad )... just ran across it...

ISNUMERIC is not a good thing to...

The problem with these types of groupings is trying to get the ranking to change where there is duplicate information, otherwise, the dupes will have the same rank.  The only...

If nothing else, it will help the developer that comes after me.

I wish more folks programmed with that...

I've heard that the SDK for SQL Server has some fairly powerful encryption tools that 3rd part software will not be able to crack.

For a lot more information on the differences between Temp Tables and Table Variables, see the following URL...

http://support.microsoft.com/default.aspx?scid=kb;en-us;305977&Product=sql2k

Wow!  Nice job of testing!  That's some awesome feedback, Peter.

It also goes to show that the machine can make a bit of a difference, as well.  My testing was done...

I'm thinking this is a bit of an orphan post...

Not really... as previously pointed out, the execution plans are identical... and so are their execution times on a quiet non-networked server... here's my test results on a million row...

This will not find the tables affected by calls to other procs within the proc identified as @objname... but it may do what you ask... and, you get some column...