Before speaking all these first what is the recovery model your database is running if its simple no ways to recover the data only to restore to your last backup...

The links below give what you want. Capturing error messages on run time. hope this will be useful for you.

http://www.sql-server-performance.com/ak_exception_handling.asp

http://www.sommarskog.se/error-handling-I.html

As jeff says it better to bounce the service to clear tempdb database.

Jeff he is speaking of 60GB tempdb file which has got increased from 200MB.

Lowell by why memory here when this is a disk operation. Why does the operation need 3GB of memory to expand the disk space. I can't understand what you say....

If you want the new identity to be generated in the destination table then don't move data from source to destination for that table. If you wat to move the...

Before you restore a database that is already being used you need to check if the database is being used by users if so kill those process so that the...

You can use @@error to track error messages in sql 2000 if its sql 2005 then use try and catch.

Better go or x86 in Windows 2000 SP4. x64 is a 64 bit version of SQL Server 2005. For more details on the bit comparisions, check http://www.microsoft.com/sql

It should be a disk problem. The disk hardening was not done properly. When you say that server frooze when the split process was done why did you then go...

Error message is not complete. Can you put a log file and track and post the error as in the log file.

It would have happened if you are not using transaction and the database is set to auto commit mode.

You can code the easily use sql to generate the script and then modify to the needed collation and then fire the script against the target DB.

Why can't you use the inbuilt SP sp_MSforeachDb to loop through databases instead of using a cursor. Try that.

If you are not confident on doing the role change and wanted to avoid unnecessary hussles then you can perform this

1. bring the database in the secondary server up after...

any bcp/bulk imports, also check the number of rows in the temp table too many rows with indexes can occupy a good number of disk space in the server.