Same here. The client tools are a standard part of each of our SQL Server installations on database servers.

With that many packages, I'd suggest you look at DTS xChange from Pragmaticworks. I've looked at it, but haven't tried it yet. http://www.pragmaticworks.com/

Hi bruce,

Despite it's name, db_dtsoperator (and the other dts roles in msdb) only works for SSIS packages. The best way I've found is to grant EXECUTE permission to...

I don't recall an option during SQL 2005 installation that let's you install DTS Designer components. I've had to download and install them after the SQL installation.

nroberson (3/31/2009)

---

Well, part of the discussion going on is do we want sa, as it is a well known account on SQL? Obviously creating a very strong, ever changing...

I know you can grant CREATE PROCEDURE permission to a user or role, which would allow it to create stored procedures, but you have to grant ALTER permission individually to...

Try granting EXECUTE permission on these stored procedures in msdb: sp_help_job, sp_help_jobstep, sp_help_jobschedule, and sp_help_jobhistory.

I would probably create a role in msdb and grant EXECUTE on the stored...

Does he only need to see the jobs or does he need more extensive permissions?

You could use undocumented sp_MSforeachdb.

sp_MSforeachdb

'use ?

--exclude system databases

if DB_ID(''?'') > 4

EXEC sp_addrolemember N''db_backupoperator'', N''LoginName''

'

Since you're apparently not storing DTS packages in Meta Data Services, you don't have to do anything. The Upgrad Advisor gives me the same results when I run it...

The backup device you see in Enterprise Manager is merely a logical name for a file where backups are stored. It has nothing to do with a backup schedule....

Actually, if you're using the view to get a list of databases, you WILL need to change the stored procedures. The compatibility level of your databases makes no difference....

Since sp_start_job runs asynchronously, it won't wait for the job to finish without you doing some work in the stored procedure. There's a post in this thread that gives...

You can also disable the schedule by opening the job, going to the Schedules tab, editing the schedule and unchecking the "Enabled" box.

Yep. Everything that goes into production gets reviewed and implemented by a DBA in our shop.