Post reply

Security on sql 2005

  • April 23, 2009 at 2:46 pm

    #203867

    I was told to change all the account password on production server. I am little scared to do that because I know if I change the password then lots of application will fail. like remove link etc.

    What is the best way to change the account password without any affect to other application.

  • April 23, 2009 at 3:04 pm

    #983285

    Definitely applications,jobs , scheduled task everything will get affected..

  • April 23, 2009 at 3:13 pm

    #983291

    You right to be hesitant. If applications are using the logins in connection strings to connect to SQL Server, there's no way you can change passwords without affecting them. You'll have to coordinate the password changes with whomever supports the applications so they can be changed simultaneously.

    Greg

  • April 24, 2009 at 7:33 am

    #983530

    You can try a couple of things to reduce the pain:

    • Use a script like the one here[/url] (add ApplicationName to the output) to use the Default Trace to find out what applications are using what logins to access the SQL Server.
    • Document the current passwords if you can, so if you have to go back you can.
    • The obvious one, proceed slowly, one at a time, and be prepared for failures by making sure members of the dev team are ready to change application settings.

    Jack Corbett
    Consultant - Straight Path Solutions
    Check out these links on how to get faster and more accurate answers:
    Forum Etiquette: How to post data/code on a forum to get the best help
    Need an Answer? Actually, No ... You Need a Question

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

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