I understand your frustration for a security hole, but, IMO, you are using
highly unappropriate language in this forum.
Ken Sedlacek
Kyrus Corporation
Office: 864-322-4260; Cell: 864-444-8375
Text Page: 864-444-7243, follow prompts
[EMAIL PROTECTED]
Kyrus IT Support (Internal: 4399) (Greenville: 864-322-4399)
(Toll-Free: 888-413-4399)
Mark
Stapleton To: [EMAIL PROTECTED]
<stapleton@BE cc:
RBEE.COM> Groups: Don't Expand
Sent by: Subject: Re: tsm sql error messages
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>
05/26/01
12:37 AM
Please
respond to
"ADSM: Dist
Stor Manager"
Del Hoobler wrote:
> Did you try specifying a valid sql userid and password?
> For example:
>
> sqldsmc /backupfull:* /SQLUSer:userid /SQLPWD:password
>
> The default is "sa" for /SQLUSER and "" (blank) for SQLPWD.
...which begs a question:
Why in the name of God's greasy gonads did the TDP for SQL group build
sqldsmc.exe's code to require that I put a password for an SQL server's
system administrator ID in *clear test*? We're in danger of losing a
customer's TDP for SQL business because that system administrator's
password has to sit out there stark naked in a batch file. The TDP for
SQL's GUI interface allows you to enter the password once and have it
encrypted. Why in *hell* can't the command-line version use that
encrypted password?
--
Mark Stapleton ([EMAIL PROTECTED])
