Matthew Ross (2/12/2007)

Lee,

... as far as using a DB for this, who cares? A DB is a data repository key word being data just as the file system (e.g....

I'm late to the discussion, but here's my cynical two cents anyway...

It will never happen, because if ANYONE ever actually delivered a relational language and platform, why would we...

Jeff, I can't and won't try to say that you are wrong on any particular point because I do agree with you that performance is critical. 

The one thing that...

That's a really excellent question, I might steal it!  It sets up a situation that lets you distinguish those who have practical experience from those who don't.  My answer 5-6...

Jeff, your point about cursors is taken, but there are situations where they are, in reality, the best solution to the problem at hand.  Like almost everything else in the...

My position has both hardened and softened somewhat over the past few years. 

I still think that XML is “a stupid answer to all the wrong questions”, and that the...

It has to do with the narrower scope of variables vs. temp tables.  Temp tables are available for all batches in a connection, variables are scoped to the batch.  Therefore...

"All else being equal" is the key phrase here, and while numbers may not lie, those who put them together certainly do.  Sowell's argument is not that women aren't compensated...

The whole "women get paid less for doing the same work" is such a tired old lie that I just can't let this pass.

No credible study has ever been able...

It makes perfect sense to have a single set of data available across the enterprise and things like Color, or EmployeeStatus etc... are very likely candidates for this, but in...

I have yet to hear a truly useful definition for Domain\Lookup\DataDictionary\etc... tables.  Why is it deemed necessary to treat them differently than any other tables?  And by extension, why is...

Jeff is correct, but doing this carries the same risks as using nolock.

If you are using SQL 2005 then Read Committed Snapshot isolation level might be an appropriate choice.

I believe it applies only to RPC and will return the objectId of the stored procedure that was called.

2,147,483,647 bytes, basically 2 Gigabytes

Object_id is not applicable to SQL:stmtStarting or ending.  You can accomplish this by putting a filter on the TextData column.  So something like "SELECT%FROM%TableName%" would probably do the trick.  Minus...