Hi Jeff,
I don't think there is a way to stop them being pre-populated. However, you
can change the owner in the sysdtspackages table by entering the name and
SID of the person you want to own the package. Use something like:
update msdb.dbo.sysdtspackages set owner = 'EUROPE\charles', owner_sid =
suser_sid(N'Europe\charles') where [name] = 'MyPackage'
The suser_sid function returns the SID of the login.
I don't know how to change the machine name. If you right-click the designer
screen and choose Disconnected Edit, you will find it's grayed out. I think
it's part of the packagedata column.
Charles Kangai, MCT, MCDBA
[quoted text, click to view] "Jeff Shipman [MSFT]" wrote:
> Our product uses a DTS job to copy between two databases. Whenever we modify
> this DTS package, we notice that the Owner and Machine fields are
> automatically filled in (when you view the Package->Properties values). The
> problem here is that usually one of our devs modifies the job on his box and
> submits it. This results in our machine names and domain username leaking
> out as part of the package. We could use one of our build machines with a
> builder account, but this still mentions internal product name data in the
> machine name. Is there a recommended way for people that ship DTS packages
> to deal with this?
>
>
>
> Thanks.
> --
> Jeff Shipman [MSFT]
> Security, Access and Solutions Division
>
>
> *This posting is provided "AS IS" with no warranties, and confers no rights.
> *Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
> *Use of any included code samples is subject to the terms specified at
>
http://www.microsoft.com/info/cpyright.htm >
>