Post reply

sysjobhistory table and sa password

  • May 27, 2003 at 8:24 am

    #64931

    I am new to SQLServer but I have noticed a surprising feature of running a job via a .cmd file. The backup job executes the .cmd file that uses OSQL to call a .sql file. Within the .cmd file is the sa user and password which is apparently written to the message column of the msdb..sysjobhistory table that I assume anyone can view !! Is there a way of either suppressing the write or somehow inhibiting the viewing of that column ?

  • May 27, 2003 at 8:46 am

    #458664

    Have you tried -E parameter in OSQL.

    -E

    Uses a trusted connection instead of requesting a password.

    Edited by - Allen_Cui on 05/27/2003 08:46:29 AM

  • May 27, 2003 at 9:15 am

    #458678

    The password shoudn't be written to the job.

    You should check the script that you are running, that doesn't print the sa password.

  • May 27, 2003 at 9:36 am

    #458682

    Thank you Allen_Cui, that works a treat.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply