http://www.sqlskills.com/BLOGS/PAUL/post/TechNet-Radio-interview-on-database-corruption.aspx

article that is what you need to know...about SQL Server Maintenance

http://sqlskills.com/BLOGS/KIMBERLY/post/Database-Maintenance-Best-Practices-Part-I-e28093-clarifying-ambiguous-recommendations-for-Sharepoint.aspx

http://www.mssqltips.com/sqlservertip/1367/sql-server-script-to-rebuild-all-indexes-for-all-tables-and-all-databases/

Remove the where clause and run

SELECT * FROM sys.server_triggers

I think You can not do sp_helptext on server level triggers. you can generate the script by ssms.

run dbcc checkdb() prior and after the restore and compare the result.

You also do it by changing the auto-close property to false of model DB.. so after attaching u don't need to change.

-2 is DTC orphan transaction to kill this ,you have to first find UOW( unit of work) from sys.dm_tran_locks

Select request_owner_guid from sys.dm_tran_locks where request_request_id = -2

Kill 'request_owner_guid'

Try with using Navarchar(MAX)

What is the question here?

You can find the actual memory usage by below query.

SELECT cntr_value AS 'Total SQL Server Memory'

FROM sys.dm_os_performance_counters

WHERE object_name = 'MSSQL$INSTANCENAME:Memory Manager'

and counter_name = 'Total Server Memory (KB)'

As you connections are in sleeping state. you can kill the connection before restoring it. A connection lifetime is depends on the connection string when it served and application...

SAN Level mirroring? / SRDF?

You cannot mirror one database to multiple instances.

Are you typing correct password?

Is SQL authentication enabled on the server?

Please elaborate.