what is the error message are you getting?

Visit following link for detail:

ms-help://MS.SQLCC.v10/MS.SQLSVR.v10.en/s10de_4deptrbl/html/da0532bd-1d3d-4483-b2ba-944b164a95be.htm

I understand that at the EOD data is important to you for reporting purpose.

You can have two solutions here:

1. Add step to use sp_sendmail after the SQL Server Agent replicate...

If your database is not production and would like to truncate tlog frequently you can set the database to the simple recovery mode. If your database is production than tlog...

In addition to this when you are doing performance & tunning at that time you need to have admin privilages to access perfmon for CPU, IO, MEMORY etc. utilization.

Try your stored proc step by step and print message e.g. "Step1 completed" and / or "step1 started" for every possible step.

Also you can use profiler for further investigation.

Good Luck!

If your server is not production and able to restart the SQL server; it will recycle tempdb at the restart.

Database Mirroring is having Interoperability and Coexistence with Other Database Engine Features like Full-text catalogs

Refer the following link for further detail:

ms-help://MS.SQLCC.v10/MS.SQLSVR.v10.en/s10de_4deptrbl/html/a7f95ddc-5154-4ed5-8117-c9fcf2221f13.htm

Hopefully there shouldn't be any problem but the only thing is you won't get advantage of 64 bit as SQL Server 2000 is for 32 bit only.

But still double check...

visit following site for the further detail:

http://msdn.microsoft.com/en-us/library/ms143393.aspx

Also you can Track changes of your Production database like Schema changes, credential changed etc. by using DDL AND DML Triggers

You can cerate the stored procedure and grant execute permission to the perticular user.

"GET RID OF INDEXES" is absolutely fantastic idea. If Microsoft has to beat the VLDB market this would be the key factor.

Also using multiple backup device alongwith "GET RID OF...

Your problem is not much clear to me.

But I understand is you are having problem in accessing the user databaes. If you are having the problem in accessing user database...

Use Database Mirroring Monitor tool to narrow down your problem. Refer the following link for further reference.

http://msdn2.microsoft.com/en-us/library/ms365809.aspx

http://msdn2.microsoft.com/en-us/library/ms365781.aspx

Also best practice:

http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/dbm_best_pract.mspx

Good Luck!