Run your profiler and chooose text data for the data column.  It will output the procedure as well as the params passed.

http://www.databasejournal.com/features/mssql/article.php/3424791

Though I hate SQL Mail - that is setting up profiles and outlook.  Its supposed to be a lot better in SQL 2005 as it uses SMTP.

Currently for my needs...

Does not matter whether Windows Adv server or windows server.  Max memory for SQL 2000 Standard edition is 2GB per server.

I agree with homebrew,  Phil was not out of line and was being helpfull. if everyone was to post messages in the wrong place - not only would he/she not get...

You could use a third party tool which supports object level recovery.  Usefull if the table that needs to be restored is part of a very large database.  

Thanks DC,

You are correct, I normally shrink it manually once or so a year.  I understand the overhead caused by constantly shrinking it. 

DBREINDEX will do that, especially on tables that have clustered indexes - you might want to backup the trans log more often when the DBREINDEX runs.

If your Trans log files are growing rapidly - I would look at backing them up on a regular basis.  Also are you defragmenting your indexes and shrinking your database...

Sounds to me like you have a memory bottle neck.  You might want to consider adding more memory and then setting a cap like Kenneth suggests.  You should genereally leave...

Using Winrar to extract from the command prompt:

Set the Winrar path first:

set path="c:\program files\winrar\";%path%

and then extract:

winrar e archive_file_name

Take a full backup of each DB - RAR them using winrar or Zip them up and copy them over. Winrar has some good compression options.

I like using winrar, simple to use and has some great build in functions.   Download it from http://www.download.com.

Like Phill says, don't mess with the Stats.  What you should do on a regular basis is to update the stats so that the optimizier has the latest stats...

Its likely a large table, then do as Quantix suggested - truncate the table and then drop the table.

Stop and restart the SQL Server Service and re-apply the last transaction log that is the one that was applying when the DB went into the loading state.