We have a VBA application that calls a SQL Server 2000 Job which calls
a DTS package to pull data from one database and populate another
database. In order to pull the data, we need to provide a password to
the connection. Currently, the VBA app populates an .ini file with the
password (provided by the app user) which the DTS package then uses to
log in to the source database.
I'm not very happy about storing a password anywhere where somebody
could find it. Can anybody suggest a better solution?
Thanks in advance,
SaulHi
Your package password can be specified on the command line using the /M or
/~M parameter, therefore you may want to pass an encrypted parameter or
possibly an encrypted command check out
http://www.sqldts.com/default.aspx?301 on getting help for running dtsrun. I
am not sure why you are running this from VBA and not using SQL Agent!
John
"saul_margolis@.hotmail.com" wrote:
> We have a VBA application that calls a SQL Server 2000 Job which calls
> a DTS package to pull data from one database and populate another
> database. In order to pull the data, we need to provide a password to
> the connection. Currently, the VBA app populates an .ini file with the
> password (provided by the app user) which the DTS package then uses to
> log in to the source database.
> I'm not very happy about storing a password anywhere where somebody
> could find it. Can anybody suggest a better solution?
> Thanks in advance,
> Saul
>|||Thanks John. I know I can pass in global variables when calling the
DTS package, but the DTS package is called by the job. I would need
some way of passing in the password to the job. Do you know if that's
possible?
John Bell wrote:
> Hi
> Your package password can be specified on the command line using the /M or
> /~M parameter, therefore you may want to pass an encrypted parameter or
> possibly an encrypted command check out
> http://www.sqldts.com/default.aspx?301 on getting help for running dtsrun. I
> am not sure why you are running this from VBA and not using SQL Agent!
> John
> "saul_margolis@.hotmail.com" wrote:
> > We have a VBA application that calls a SQL Server 2000 Job which calls
> > a DTS package to pull data from one database and populate another
> > database. In order to pull the data, we need to provide a password to
> > the connection. Currently, the VBA app populates an .ini file with the
> > password (provided by the app user) which the DTS package then uses to
> > log in to the source database.
> >
> > I'm not very happy about storing a password anywhere where somebody
> > could find it. Can anybody suggest a better solution?
> >
> > Thanks in advance,
> > Saul
> >
> >|||Hi
I am not sure why you need to do this as the password for any given package
would be relatively fixed! It is not passed as a global variable by it's own
argument on the command line.
If you ran the package from a stored procedure it could pick up the package
name and other parameters from a table
http://www.sqldts.com/default.aspx?210, alternatively use the /Z parameter
and encrypt the whole command and keep the ini file. You could also use a
table of encrypted commands!!
John
"saul_margolis@.hotmail.com" wrote:
> Thanks John. I know I can pass in global variables when calling the
> DTS package, but the DTS package is called by the job. I would need
> some way of passing in the password to the job. Do you know if that's
> possible?
>
>
> John Bell wrote:
> > Hi
> >
> > Your package password can be specified on the command line using the /M or
> > /~M parameter, therefore you may want to pass an encrypted parameter or
> > possibly an encrypted command check out
> > http://www.sqldts.com/default.aspx?301 on getting help for running dtsrun. I
> > am not sure why you are running this from VBA and not using SQL Agent!
> >
> > John
> >
> > "saul_margolis@.hotmail.com" wrote:
> >
> > > We have a VBA application that calls a SQL Server 2000 Job which calls
> > > a DTS package to pull data from one database and populate another
> > > database. In order to pull the data, we need to provide a password to
> > > the connection. Currently, the VBA app populates an .ini file with the
> > > password (provided by the app user) which the DTS package then uses to
> > > log in to the source database.
> > >
> > > I'm not very happy about storing a password anywhere where somebody
> > > could find it. Can anybody suggest a better solution?
> > >
> > > Thanks in advance,
> > > Saul
> > >
> > >
>|||Hi John,
It's not actually the password for the package that is needed. It's
the password that the package will use to login to the server which
contains the source data.
John Bell wrote:
> Hi
> I am not sure why you need to do this as the password for any given package
> would be relatively fixed! It is not passed as a global variable by it's own
> argument on the command line.
> If you ran the package from a stored procedure it could pick up the package
> name and other parameters from a table
> http://www.sqldts.com/default.aspx?210, alternatively use the /Z parameter
> and encrypt the whole command and keep the ini file. You could also use a
> table of encrypted commands!!
> John
>
> "saul_margolis@.hotmail.com" wrote:
> > Thanks John. I know I can pass in global variables when calling the
> > DTS package, but the DTS package is called by the job. I would need
> > some way of passing in the password to the job. Do you know if that's
> > possible?
> >
> >
> >
> >
> > John Bell wrote:
> > > Hi
> > >
> > > Your package password can be specified on the command line using the /M or
> > > /~M parameter, therefore you may want to pass an encrypted parameter or
> > > possibly an encrypted command check out
> > > http://www.sqldts.com/default.aspx?301 on getting help for running dtsrun. I
> > > am not sure why you are running this from VBA and not using SQL Agent!
> > >
> > > John
> > >
> > > "saul_margolis@.hotmail.com" wrote:
> > >
> > > > We have a VBA application that calls a SQL Server 2000 Job which calls
> > > > a DTS package to pull data from one database and populate another
> > > > database. In order to pull the data, we need to provide a password to
> > > > the connection. Currently, the VBA app populates an .ini file with the
> > > > password (provided by the app user) which the DTS package then uses to
> > > > log in to the source database.
> > > >
> > > > I'm not very happy about storing a password anywhere where somebody
> > > > could find it. Can anybody suggest a better solution?
> > > >
> > > > Thanks in advance,
> > > > Saul
> > > >
> > > >
> >
> >|||Hi
Can you not used the /E parameter?
John
"saul_margolis@.hotmail.com" wrote:
> Hi John,
> It's not actually the password for the package that is needed. It's
> the password that the package will use to login to the server which
> contains the source data.
>
> John Bell wrote:
> > Hi
> >
> > I am not sure why you need to do this as the password for any given package
> > would be relatively fixed! It is not passed as a global variable by it's own
> > argument on the command line.
> >
> > If you ran the package from a stored procedure it could pick up the package
> > name and other parameters from a table
> > http://www.sqldts.com/default.aspx?210, alternatively use the /Z parameter
> > and encrypt the whole command and keep the ini file. You could also use a
> > table of encrypted commands!!
> >
> > John
> >
> >
> >
> > "saul_margolis@.hotmail.com" wrote:
> >
> > > Thanks John. I know I can pass in global variables when calling the
> > > DTS package, but the DTS package is called by the job. I would need
> > > some way of passing in the password to the job. Do you know if that's
> > > possible?
> > >
> > >
> > >
> > >
> > > John Bell wrote:
> > > > Hi
> > > >
> > > > Your package password can be specified on the command line using the /M or
> > > > /~M parameter, therefore you may want to pass an encrypted parameter or
> > > > possibly an encrypted command check out
> > > > http://www.sqldts.com/default.aspx?301 on getting help for running dtsrun. I
> > > > am not sure why you are running this from VBA and not using SQL Agent!
> > > >
> > > > John
> > > >
> > > > "saul_margolis@.hotmail.com" wrote:
> > > >
> > > > > We have a VBA application that calls a SQL Server 2000 Job which calls
> > > > > a DTS package to pull data from one database and populate another
> > > > > database. In order to pull the data, we need to provide a password to
> > > > > the connection. Currently, the VBA app populates an .ini file with the
> > > > > password (provided by the app user) which the DTS package then uses to
> > > > > log in to the source database.
> > > > >
> > > > > I'm not very happy about storing a password anywhere where somebody
> > > > > could find it. Can anybody suggest a better solution?
> > > > >
> > > > > Thanks in advance,
> > > > > Saul
> > > > >
> > > > >
> > >
> > >
>
No comments:
Post a Comment