Here is a procedure to script the logins, but for log shipping you can make use of transfer login tasks as mentioned abovehttp://support.microsoft.com/kb/246133

Please check if the below link was helpful,

http://deepakrangarajan.blogspot.com/2008/01/mcts-70-431-exam-useful-links.html

Good Luck!

Please refer this link which might answer your question, http://sql-articles.com/index.php?page=articles/lship/lship.htm

Just an additional information ! in Sql 2005 you have this option to reset a passsword even if you don't know the password of any sysadmin Id refer this LINK...

For connecting remotely using SSMS you need to have configured permissions to the DCOM config node and provide access permissions to connect to SSIS. Refer this link for more info,

http://deepakrangarajan.blogspot.com/2008/03/connecting-to-integration-service-on.html

Are you taking transaction log backup and then shrinking ? Refer this which explains about [font="Verdana"]Log file growth in Sql Server.[/font]

Yes you can copy the backup file to another server and verify them using the following command,

Restore verifyonly from disk='Path\filename.bak'

Also ensure that nobody has truncated the log file using Backup log with truncate_only or no_log command. Because the usage of the above commands will break the LSN and hence...

Please refer this link which might help you begin with analyzing deadlock.

http://code.msdn.microsoft.com/SQLExamples/Wiki/View.aspx?title=Troubleshoot%20Deadlocking%20in%20SQL%20Server

You need to make use of the trace flag 1222 and 3605 to analyze the same.

Yes you can make it possible by using sp_configure options. You need to enable scan for startup procedure option. Refer this links for more info,

http://weblogs.sqlteam.com/mladenp/archive/2007/08/14/60280.aspx

http://technet.microsoft.com/en-us/library/ms191129.aspx

Configure a job to check the log file growth every 24 hours. You can get the desired information from sys.database_files catalog view and configure a mail alert with those details

Have a look at all the below links. The upgradation procedure is same as that of Sql 2000 to Sql 2005. The steps are mentioned in the below links.

You can have any naming convention, we generally use .bak for full/diff backup and .trn for transaction log backup. You can even have the file extension similar to .deepak..it will...

Detach all your user databases and keep it in a safer location. Install 64 bit and attach all the user databases. The only difference between detach/attach and backup/restore is that...

This link might help you,

http://doc.ddart.net/mssql/sql70/8_con_03_20.htm