Create login XYZ on destination server and keep that all the time.

Whenever you restore DB1 from source to destination server this arrangement will work without removing anything from DB.

if...

Try this 2 queries this will give you the details you are looking for

SELECT sj.name AS JobName,Count(*) AS COUNT,

AVG(( run_duration % 100 )+ ...

This is feature in Management studio 2005 and was not in Enterprise Manager of Sql Server 2000

Auto Shrink need to be used with utmost caution.

This is off by default but in any case if you switch this  on then server will periodically check, if shrink is...

FOR format mm/dd/yy  ( 06/26/06 )

Select convert (datetime, '6/25/2006') 

will convert your varchar to datetime.  Instead of '6/25/2006' you can use variable provided you feed that variable with mm/dd/yy.

Yes, that is viable. Make sure you change version from 8 to 9.

In Mgmt. Studio Right Click Restored DB to go to Properties

Choose Option and change compitibility level to Sql Server 2005(90).

Check the following article by MAK, In that he has come up with one  UDF that basically includes 3 different way we generally use to check the file status.

http://www.databasejournal.com/features/mssql/article.php/10894_3492046_1

HTH,

SELECT TYPE,NAME FROM SYSOBJECTS WHERE TYPE = 'FN'

IN YOUR QUERY ANALYZER EXECUTE THIS QUERY.

I AM NOT FOLLOWING WHAT YOU MEAN BY NOT IN SYSOBJECTS.

#table_name (local), ##table_name(global) are always created in tempdb on disk. Check this article which will provide you better insight for all temp table issues.

http://databases.aspfaq.com/database/should-i-use-a-temp-table-or-a-table-variable.html

To avoid this issue in future better script a job that checks Transaction Log,

have code for Transaction log backup with truncate_only

followed by shrink log file  and full DB backup.

You can probably use Cursor, but again that will be very expensive

on performance part  or else try using XML output.

for RAID registry key Check this microsoft details 

http://support.microsoft.com/kb/149927/EN-US/

Windows NT stores information pertaining to disks, drive-letter assignments, and RAID sets in the registry. The information is located in the following...

Try Full outer join, something like

select * from customers full outer join profile 

   on customers.custid = profile.custid

For Update better use set based t-sql and avoid cursor.

Cursors are very expensive in terms of performance.

No need for transaction log for MSDB DB.

When you make some major changes in Job etc.

To make sure that you do not loose that change

due to any accidental...