SQL Server 2005 Notification Services is a built-in component. It is not displayed in your computer services. Correct me if I am wrong.

How about

BACKUP DATABASE dbName TO DISK = '\\targetServer\$mapDrive'

You need to have authority to create a mapping drive in the above approach.

You can also create a database device first.

After backing...

How about

UPDATE tableName SET colName = ... WHERE colName LIKE '%1111'

?

Did you set your SQL Server Agent auto-start? You can set it either on the Windows services or the properties of SQL Server.

Did you try SELECT * FROM master..sysprocesses?

You may have to provide field names when values you provided do not match the default.

To truncate a file,

DBCC SHRINKFILE (FL_W20060730, EMPTYFILE)

DBCC SHRINKFILE (FL_W20060730, TRUNCATEONLY)

to truncate inactive logs,

BACKUP LOG dbName WITH TRUNCATE_ONLY

Are they helpful?

You should detach the passive node.

Do the hardware upgrade.

Add the node.

Failover the node.

Detach the passive node.

Upgrade the hardware on the passive node.

Attach the node.

Did you try to run

RESTORE DATABASE dbName WITH RECOVERY?

I guess you do not have privilege to view all columns in this table.

Changing complevel helps, but may not solve all of your issues. To know whether or not it fits your case, you need to do more tests.

You can set up your notification profile. It is not quite easy to build the notification profile on SQL Server 2000. You may use other tools to send email notifications....

Notification is one of tasks under SQL Server Agent. My suggestion is: start an alert and see if you are notified.

Did you try to set complevel to 80?

A script can do it in a snap. Look at the table, sysusers, in any database. Anyone, who has either dbo, sa, ..., can do it.