"Dora Manjula." wrote:

> Hi Gouti,
>
> The way we fixed the problem is by storing the credentials in XML file. Our
> master package uses an XML file where it gets all the connection information
> and the child package also references the same XML file. We decided not to
> encrypt the password or store it in the package as it had quite a few
> limitations.
>
> Thanks,
> Dora.
>
> "Gouti" wrote:
>
> > Hi all,
> >
> > Has anyone found concrete solution to the issue Dora described. I have the
> > same problem as well. I have 20 sub packages called from a single master
> > package.
> > The password option for sub package configuration does not appear when
> > trying to
> > configure using xml file.
> >
> > Thank you !
> >
> >
> > "Cédrick" wrote:
> >
> > > Hi Dora,
> > >
> > > Well you could store your passwords and connection information in an XML
> > > configuration file... did you tried that option?
> > > If no, you can add configuration file to a package by clicking on the BIDS
> > > menu -SSIS - Package Configuration
> > > Then check the box "enable package configuration" then clic on the "add"
> > > button.
> > > And a wizard appears to define this configuration file.
> > >
> > > Hope this helps.
> > >
> > > Regards
> > >
> > > Cedrickb
> > >
> > > "Dora Manjula." wrote:
> > >
> > > > How do I do it using the parent variable configurations ? The way I am doing
> > > > it now is to assign a password to the child package and am storing that
> > > > password in the password property on the execute package task in master
> > > > package. I thought I cannot assign the value to the password property through
> > > > expressions. Am I wrong ? Then I also had to encrypt my master package
> > > > because without this, it wouldnt save the child password on the execute
> > > > package task. The master password is what I am passing in the cmd line. I
> > > > dont like this approach as this is not easy to maintian. If we ever needed to
> > > > change the password(if the password ever created a security threat), I would
> > > > have to manually open each of my 700 packages and do this. Instead it would
> > > > be easier to change a SQL Server table maybe. Is there anyway I can make this
> > > > more dynamic ?
> > > >
> > > > Thanks,
> > > > Dora.
> > > >
> > > > "Allan Mitchell" wrote:
> > > >
> > > > > Hello Dora Manjula.,
> > > > >
> > > > > If you look at DTExecUI it will help you here.
> > > > >
> > > > > I would decrypt the master package on the cmdline as normal using a password
> > > > > and I would also pass this password in to the package (Configuration or through
> > > > > the cmdline).
> > > > >
> > > > > You can then use the Execute Package task inside the master package and assign
> > > > > the value passed in to the correct property on this Task.
> > > > >
> > > > > If you need to go even more levels deep then I would look at Parent Variable
> > > > > configurations.
> > > > >
> > > > > Make sense?
> > > > >
> > > > > --
> > > > >
> > > > > Allan Mitchell
> > > > > http://wiki.sqlis.com | http://www.sqlis.com | http://www.sqldts.com |
> > > > > http://www.konesans.com
> > > > >
> > > > > > Thanks Allan.
> > > > > > My problem is a little more complicated because I call this package
> > > > > > from a
> > > > > > master SSIS package and the master SSIS package is scheduled and so
> > > > > > uses
> > > > > > dtexec command. In this case , if I choose "EncryptAllWithPassword"
> > > > > > for the
> > > > > > childpackage, how can I pass that from the command line to the master
> > > > > > package
> > > > > > and how will the master package use this to decrypt the child package
> > > > > > ?
> > > > > > Thanks,
> > > > > > Dora.
> > > > > > "Allan Mitchell" wrote:
> > > > > >
> > > > > >> Hello Dora Manjula.,
> > > > > >>
> > > > > >> You could always encrypt this in the package using one of the
> > > > > >> ProtectionLevel settings. If you choose to Save Password and choose
> > > > > >> to Encrypt then the password will be stored encrypted. This may
> > > > > >> present issues when it is not you running the package if you choose
> > > > > >> EncryptSensitiveWithUserKey.
> > > > > >>
> > > > > >> Personally I always choose DontSaveSensitive and I pass in the value
> > > > > >> of Sensitive information from a Configuration.
> > > > > >>
> > > > > >> I lock down the configurations should they be on the file system or
> > > > > >> in a database table.
> > > > > >>
> > > > > >> --
> > > > > >>
> > > > > >> Allan Mitchell
> > > > > >> http://wiki.sqlis.com | http://www.sqlis.com | http://www.sqldts.com
> > > > > >> |
> > > > > >> http://www.konesans.com
> > > > > >>> My source connection is a SQL Server in SSIS and I use SQL
> > > > > >>> Authentication. So I provide the user id and password in the source
> > > > > >>> connection. When I check the object into Source safe and check it
> > > > > >>> out, tha password is not saved. This was never a problem in the DTS
> > > > > >>> world. Also, I dont want to give the password as cleartext in config
> > > > > >>> file. Other than setting a password to the package is there anyway
> > > > > >>> around this ?
> > > > > >>>
> > > > > >>> Thanks,
> > > > > >>> Dora Manjula.
> > > > >
> > > > >