This is the best info I've received.  In our datawarehousing environment, we are always working with result sets that are in the tens of thousands rows, sometimes in the millions. ...

And thank you too, Sergiy.

Thanks, noeld.  I was thinking that "it depends".  Obviously, large volumes in a OLAP batch reporting environment equates to the use of temp tables and not table variables.  Thanks again.

Kimball is terrific...  but don't leave out the writings of Bill Inmon.  Even though Inmon presents the non-dimensional approach, he still has a lot to say.

Also, check out datawarehouse.com, which...

As I referred to previously, I work in a SQL datawarehouse/analysis/reporting environment where it's ALWAYS advantageous, both from flexibility and a performance point of view, to use a stored procedure.  We...

There is a place where you almost always want a stored procedure and that is in retrieving data from a data warehouse/dimensional model where there may be a number of...

This is perfect.  Thanks ever so much.

Steve's article has a log of merit.  AND... if your database and servers are protected via security setups, then why encrypt the entire database?  In the healthcare field, it's required...

I depends on your application.  If this is in a reporting environment, and querys can take several minutes to run, then what difference does a few seconds make.  If it's...

Thank you very much.  That was much too easy.

I have found that table variables have their limitations.  In a datawarehouse environment, with query results totaling hundreds of thousands of rows, or more, table variables are NOT the way...

I REALLY like the script at

http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=246

Thanks, Frank.  I'm adding that to my toolkit.

Detach the DB's on the old server, copying them to the new (over the network, via tape, or whatever), then attaching them on the new is (usually) a piece of...

I'm sure ArcServe does NOT take care of the transaction logs the way SQL Server maintenance jobs do.  I agree with Quynh.  That's about the only way I can think...

I'm a firm believer in the use of temp tables, especially when using stored procedures in datawarehouse/decision support environments, where you always have tables with rows in the millions, often...