Answered OBDC data sources.

  • Sunday, January 13, 2013 8:39 PM
     
     

    Hi Guys

    One of the applications i have installed requires ODBC data source to talk to the SQL database 2008.

    I have tested the created ODBC using the SA account and it tested succcessfully.

    DOES THE odbc PROFILE SAVES THE password or not?

    Does it be an issue if the DB admin changes the password for the SA account to something.

    Will the application still be able to talk to the database server if the password is changed.

All Replies

  • Sunday, January 13, 2013 8:51 PM
    Moderator
     
     

    DOES THE odbc PROFILE SAVES THE password or not?

    No, the SQL Server ODBC drivers do not save the password used to test the connection interactively.  With SQL Server authentication, the application must provide the SQL Server login and password.


    Dan Guzman, SQL Server MVP, http://www.dbdelta.com

  • Sunday, January 13, 2013 8:58 PM
     
     

    thanks dan,

    THe application was configured and installed pointing to the correct database and with correct login and password.(SA account was used)

    Now the Db admin has changed the password (SA account),

    IT seems that the application is nt working ok now.

    THE  application has a file which it reads when started. This is text file wih the ODBC profile name the application uses

    Do you think that the application working is not ok because of the changing of the password.

    Regards

  • Sunday, January 13, 2013 9:36 PM
    Moderator
     
     Answered

    Do you think that the application working is not ok because of the changing of the password.

    The application need both the login name and the password to connect, or use Windows authentication.  If it was connecting fine before the SA password change but not afterward, it seems the application is still configured to use SA along with the old password. 

    I can't speak to the specific app you are installing but there should be a way to specify both the login and password.  The best practice is to avoid using a privileged account like SA for routine application functionality.


    Dan Guzman, SQL Server MVP, http://www.dbdelta.com