When an existing instance is upgraded, the instance name will remain the same. If it was a named instance before upgrade, it will continue to use the same after upgrade...

You can make use of the Default Trace to get that information. Here is a good example.

If you have SSMS 2005 or above installed somewhere on the network, please connect to the SQL Server 2000 instance using that. You can easily script out the jobs by...

You can make use of SMO.

http://msdn.microsoft.com/en-us/library/microsoft.sqlserver.management.smo.agent.job.aspx

http://msdn.microsoft.com/en-us/library/ms186273(SQL.90).aspx

If the secondary database is in "Standby" mode, it is available for Read-only access.

Try adding an output file to the job step. It should give more information regarding the job execution.

Was it working earlier? If yes, you can try stopping DBMail and starting it again.

exec sysmail_stop_sp

go

exec sysmail_start_sp

go

You can make use of sp_help_revlogin

You can make use of DTEXEC.EXE to schedule SSIS packages from the command prompt

You need to edit the <ServerName>...

For moving the files across ROBOCOPY is very useful utility to have.

Yes you can do manual failover.

Try opening the server in "public network" in Windows Explorer. If it does not, then there may be...

Hi Raghavender,

You can workaround this situation by altering the login as in the below script. More details here[/url]

ALTER LOGIN [LoginName]

WITH

CHECK_POLICY = OFF,

CHECK_EXPIRATION = OFF

You can RESTORE the database WITH MOVE. With this you can move the data and log files to a new location. More details here