I have been trying different combinations of permissions
but can't seem to find the minimum needed to create DTS
Packages. I am administrering a shared server across
multiple clients. I need to allow the clients the
ability to create DTS packages but not access each other
databases. Any direction would be appreciated.

Thom

In message <14ae01c47bba$dfabfaa0$a501280a (AT) phx (DOT) gbl>, Thom
<anonymous (AT) discussions (DOT) microsoft.com> writes
Your require no permissions to create a package. DTS is COM, so if you
have the COM objects you can do this. By default, using Enterprise
Manager any user can create a package and store it in the Local Packages
store, which is really just msdb. The sp_adddtspackage procedure for
example defaults to execute for the public role.

To stop users accessing other users databases then don't give them
permissions for those databases. To stop users accessing other users
packages, if stored in local packages then you could hack the system
procs, but probably a bit severe for your if not familiar, and of course
unsupported but still workable, so just tell users to password the
packages.


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org