Hopefully you took a backup of the 2005 database?

xp_servicecontrol 'querystate', 'SQLSERVERAGENT'

Check the contents of this table:

[msdb].[dbo].[syssubsystems]

Check this directory:

Program Files\Microsoft SQL Server\MSSQL.(*)\MSSQL\binn

or this one:

Program Files\Microsoft SQL Server\90\COM

It sounds like stuff got removed from one of these locations.

I'm sure you will get several responses for third party tools such as RedGate or Idera, but for some free tools, you can read this:

http://www.sqlservercentral.com/articles/Miscellaneous/2959/

Have you verified the server name as suggested by the error message?

Is the SSIS service running?

Have you checked the following link?

http://www.sqlanswers.com/Software/SAM/SAMOnlineDemo.aspx?demo=10

Yes, on the Feature Selection screen, make sure that only Client Components is checked.

It should not require SQL Server to stop, and as long as there are no locked files...

Your most likely culprit is that this database is being restored from another copy somewhere (restoring Prod onto Development once per week to refresh data, for example).

That will alter the...

You should read up on sp_change_users_login stored procedure.

If a windows login is disabled, you will receive an error when trying to access its properties (unless you are doing so under an sa account, in which case you...

1. @email_address = nvarchar(100) (sp_add_operator)

2. No, you can only choose one.

Using database mail, though, you can get around this, I believe, by executing stored procedure msdb.dbo.sp_send_dbmail. The @recipient parm...

Thanks.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\

You can use a SQL Express datasource within an SSIS package, but the SSIS runtimes do not come with SQL Express. In other words, SSIS is compatible with SQL...

Interesting and helpful... bookmarked.