Is anyone aware of such a restriction? All my SQL Jobs etc run fine with my
SA account & password that includes both a # and a ^, but when I try to run
jobs from OSQL the job fails with a bad password error. Naturally, I have
double checked the password entry. I have also tried running a simple oqsl
job under an account that uses just plain aplhanumeric characters in the
password & that runs fine.
Thanks,
Nick.use double quotation marks (")... osql -S<server> -U<user> -P <"password">
"Nick" wrote:
> Is anyone aware of such a restriction? All my SQL Jobs etc run fine with my
> SA account & password that includes both a # and a ^, but when I try to run
> jobs from OSQL the job fails with a bad password error. Naturally, I have
> double checked the password entry. I have also tried running a simple oqsl
> job under an account that uses just plain aplhanumeric characters in the
> password & that runs fine.
> Thanks,
> Nick.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment