Hi, I have created a DTS Package in SQL Server 2000, is there any way that a
different user can edit and execute that DTS WITHOUT having server roles or
privileges?


Thanks

Elidas,

If you store your DTS Package in msdb, then it is under those msdb security
rules and elevated rights are needed.

However, if you store your DTS Package in structured file storage, then it
is under file system security. You can keep it in a folder where two or
more people have rights to edit the package.

Alternatively, if you want to keep it in msdb, you could always use a
special shared login to edit that package. Then whoever has the password to
the shared login could login, edit the package, then log back out. (I don't
really like this one, but maybe you would.) Again, the shared login would
own the package so anyone else would need elevated rights to change the
package.

RLF

"Elidas" <Elidas (AT) discussions (DOT) microsoft.com> wrote

Elidas,

If you store your DTS Package in msdb, then it is under those msdb security
rules and elevated rights are needed.

However, if you store your DTS Package in structured file storage, then it
is under file system security. You can keep it in a folder where two or
more people have rights to edit the package.

Alternatively, if you want to keep it in msdb, you could always use a
special shared login to edit that package. Then whoever has the password to
the shared login could login, edit the package, then log back out. (I don't
really like this one, but maybe you would.) Again, the shared login would
own the package so anyone else would need elevated rights to change the
package.

RLF

"Elidas" <Elidas (AT) discussions (DOT) microsoft.com> wrote

Elidas,

If you store your DTS Package in msdb, then it is under those msdb security
rules and elevated rights are needed.

However, if you store your DTS Package in structured file storage, then it
is under file system security. You can keep it in a folder where two or
more people have rights to edit the package.

Alternatively, if you want to keep it in msdb, you could always use a
special shared login to edit that package. Then whoever has the password to
the shared login could login, edit the package, then log back out. (I don't
really like this one, but maybe you would.) Again, the shared login would
own the package so anyone else would need elevated rights to change the
package.

RLF

"Elidas" <Elidas (AT) discussions (DOT) microsoft.com> wrote

Elidas,

If you store your DTS Package in msdb, then it is under those msdb security
rules and elevated rights are needed.

However, if you store your DTS Package in structured file storage, then it
is under file system security. You can keep it in a folder where two or
more people have rights to edit the package.

Alternatively, if you want to keep it in msdb, you could always use a
special shared login to edit that package. Then whoever has the password to
the shared login could login, edit the package, then log back out. (I don't
really like this one, but maybe you would.) Again, the shared login would
own the package so anyone else would need elevated rights to change the
package.

RLF

"Elidas" <Elidas (AT) discussions (DOT) microsoft.com> wrote

Elidas,

If you store your DTS Package in msdb, then it is under those msdb security
rules and elevated rights are needed.

However, if you store your DTS Package in structured file storage, then it
is under file system security. You can keep it in a folder where two or
more people have rights to edit the package.

Alternatively, if you want to keep it in msdb, you could always use a
special shared login to edit that package. Then whoever has the password to
the shared login could login, edit the package, then log back out. (I don't
really like this one, but maybe you would.) Again, the shared login would
own the package so anyone else would need elevated rights to change the
package.

RLF

"Elidas" <Elidas (AT) discussions (DOT) microsoft.com> wrote

Elidas,

If you store your DTS Package in msdb, then it is under those msdb security
rules and elevated rights are needed.

However, if you store your DTS Package in structured file storage, then it
is under file system security. You can keep it in a folder where two or
more people have rights to edit the package.

Alternatively, if you want to keep it in msdb, you could always use a
special shared login to edit that package. Then whoever has the password to
the shared login could login, edit the package, then log back out. (I don't
really like this one, but maybe you would.) Again, the shared login would
own the package so anyone else would need elevated rights to change the
package.

RLF

"Elidas" <Elidas (AT) discussions (DOT) microsoft.com> wrote

Elidas,

If you store your DTS Package in msdb, then it is under those msdb security
rules and elevated rights are needed.

However, if you store your DTS Package in structured file storage, then it
is under file system security. You can keep it in a folder where two or
more people have rights to edit the package.

Alternatively, if you want to keep it in msdb, you could always use a
special shared login to edit that package. Then whoever has the password to
the shared login could login, edit the package, then log back out. (I don't
really like this one, but maybe you would.) Again, the shared login would
own the package so anyone else would need elevated rights to change the
package.

RLF

"Elidas" <Elidas (AT) discussions (DOT) microsoft.com> wrote

Elidas,

If you store your DTS Package in msdb, then it is under those msdb security
rules and elevated rights are needed.

However, if you store your DTS Package in structured file storage, then it
is under file system security. You can keep it in a folder where two or
more people have rights to edit the package.

Alternatively, if you want to keep it in msdb, you could always use a
special shared login to edit that package. Then whoever has the password to
the shared login could login, edit the package, then log back out. (I don't
really like this one, but maybe you would.) Again, the shared login would
own the package so anyone else would need elevated rights to change the
package.

RLF

"Elidas" <Elidas (AT) discussions (DOT) microsoft.com> wrote

Thanks, but, how do I store in a different location than msdb? I though that
all DTS must be in msdb database

"Russell Fields" wrote: