I guess I should pay attention to which forum I'm in. Sorry about that.

What happened when you tried:

Grant ALTER on storedprocedure to user?

In a practical sense, Mani Singh is right. The Dynamic Management Views replace the system tables you're used to seeing in SQL 2000. In a strict sense, system...

Specifically, it would be

sp_start_job @job_name='your jobname', @step_name = 'your stepname'

The green flag indicates the starting step i.e. the first step that will run when the job starts.

I don't see any way to prevent a sysadmin member from restoring a backup. You can minimize the risk by having a minimal number of responsible people as sysadmins.

By "sequence", do you mean a column with the Identity property? If so, it's a mistake to be concerned with either the order of rows or gaps in identity...

Use msdb.dbo.sysschedules.

Yes. See "context switching" in BOL.

Try using WITH EXECUTE AS 'dbo' in the stored procedure to switch context to an user that can do TRUNCATE and DBCC CHECKIDENT. Then you just grant the user...

Rather than granting SELECT on sysdtspackages, you could try granting EXECUTE on sp_enum_dtspackages and sp_get_dtspackage in msdb.

When you right-click on the job and select 'Start Job', you'll be able to choose the step you want to start, if it's a multi-step job.

Note that the job will...

Importing DTS packages and running them as legacy packages is a good choice if you want to take your time migrating them to SSIS. That's the route we've chosen...

I'm not familiar with Protection Level as it relates to DTS packages. I've only used it with SSIS packages.

Deepak is correct. Make the job step type Operating system(CmdExec) and use DTSRun just like you did in SQL 2000 jobs.