Re: MS-SQL Agent connection error
2000-05-05 13:51:30
Subject: |
Re: MS-SQL Agent connection error |
From: |
Del Hoobler <hoobler AT US.IBM DOT COM> |
Date: |
Fri, 5 May 2000 13:51:30 -0400 |
Larry,
Actually, the GUI is the only one that will read
the registry for those stored values for
SQL server logon.
You must user /SQLUSER and /SQLPWD options
to send it for the command-line client.
If you are worried about security then you
should use the /SQLSECURE option that uses
your Windows NT login information for
SQL server access.
OK, So, now you are asking why does it work for 4 out of 5
of your servers... Well it must be that you still have
the default userid and password (userid:"sa" password:"")
defined to your SQL server. SQL Server install
gives you these as a default when you install.
If you don't specify SQLUSER or SQLPWD, it uses
the values I specified above by default.
Thanks,
Del
----------------------------------------------------
Del Hoobler
Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com
Lawrence Clark <Larry_Clark AT THRUWAY.STATE.NY DOT US>@VM.MARIST.EDU> on
05/05/2000 11:30:50 AM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: MS-SQL Agent connection error
Del:
I did try adding the /SQLPWD password parm to the command line and firing
it off in a DOS prompt and it worked.
Would you know why it might be required on this one server and not the
others. I do have the password set via the GUI interface with the save
password selected, and the GUI does do the backup without a prompt for a
password.
I thought the password was encrypted and stored and accessible when the
command line or script was executed.
Larry Clark
NYS Thruway Authority
|
|
|