Hello All,
Wondering if anyone ahs thoughts on what the best practice for ownership of
a DTS package is?

We have several biz-critical packages that are owned by individual
developers.
One of the owner/developers has recently terminated employment and we wish
to remove the associated login.

Obviously this will create problems.

Moving forward I wondered what any of the gurus present here would recommend
as a bets practice for this type of thing as well as pros/cons?

Thanks in advance.

Tam.

You can drop the login that owns the package - it won't
break anything. There is a good discussion on ownership at
sqldts.com:
Package Ownership Issues
http://www.sqldts.com/default.aspx?212

-Sue

On Wed, 16 Aug 2006 18:05:56 GMT, "Tam OShanter"
<tam (AT) oshanter (DOT) com> wrote:

Thanks for the info. Sue it was of assistance.

I'm looking for ideas on what user to make the owner of a given DTS package
in a production environment.

Thoughts on best practices for this scenario?

What do you folks do?


Thx.

Tam

"Sue Hoegemeier" <Sue_H (AT) nomail (DOT) please> wrote

I don't pay any attention to it and don't worry about it
really. Never had any problems with it. As the article says,
ownership is generally not an issue. Non-sysadmins don't
make changes in production in the environments I've worked
in so there wouldn't be anything to cause any issues.

-Sue

On Wed, 16 Aug 2006 21:33:19 GMT, "Tam OShanter"
<tam (AT) oshanter (DOT) com> wrote: