Check Database Mirroring Role Change and Automatic Failover at

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

and http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirfaq.mspx

If you do not have profiler, trace or some other utilities like foglight,.. etc. in place than there are not many options in sql server to look at past incidents....

You can add few more items to your list

1 check the compitibility of db on 2005 server after db restore from 2000 to make sure you have 90.

2. Update statistics...

Check the following details, from MSDN

SQL Server 2005 uses the Address Windowing Extensions (AWE) API to support very large physical memory sizes. SQL Server 2005 supports up to a maximum...

You can use Rebuild index / Reorganize index say once in week or monthbased on Insert/updates to your DB.

If you are using Sql 2005 there is script in MSDN...

You can kill the process, thats the right thing to do, that too will show status Killed\Rolled back for sometime.

In my experience it's still better to kill job and you...

You need DDL Triggers which is new feature of Sql Server 2005.

I am not going in the details here as you can check some book on that...

I think you are looking for SP with parameters, there are volumes of article out there to learn, probably you are looking for something like

CREATE PROCEDURE SP_UpdateStaff

@staf_num int

AS

Update tbl_staff

SET...

You can write your own SSIS where you define various task, i.e. backup db, remove db file from specific folder etc.

basically this is what Maintenance Plan does behind the...

No process is on the other end of pipe can be caused by bad certificate

check the following link,and see if it's useful in your case

http://blogs.msdn.com/sql_protocols/archive/2006/07/26/678596.aspx

If you are dealing with prime time production server than I suggest better

option is to allow windows admin or Sr. DBA with expertise to handle cluster situation, you can learn...

If you have not made any arrangement to store the date previously,

sql server will not store insert date/time for previous records.

One way, if its possible is to add InsertDate in table and default that column as getdate().

Second option is to store the getdate() value in some variable and basically flush...

ALTER DATABASE tempdb MODIFY FILE (NAME = 'tempdev', SIZE = target_size_in_MB)

requires sql server restart so that's not an option in production server.

Backup log tempdb with no_log is not...

Create new login and user in Source DB with readonly access to DB.

Use SP_help_Revlogin SP on primary server and from the output

copy your newly created login details, execute that...