Quick question about sa password

[35mph]

probably obvious, but...

Our client long ago set up a Great Plains sa password that is too easy to figure out. We would like to change it.

We need to change it in SQL Server in Enterprise Manager > Security > Logins, yes?

If we do that, won't that disable each user's local ODBC settings, which have been setup with "SQL Server Authentication" and to "Connect to SQL Server" using the sa login? (And if I'm not mistaken, is that not the way Great Plains recommends that it be setup?)

What would be a better way to set up workstation ODBC in the future... so we can login to Great Plains using the sa password, but if we change it in SQL Server we don't have to change it on everybody's ODBC?

 

[35mph]

Follow-up question:

Ok, we just changed it in SQL Server, and we were still able to connect as sa in Great Plains... without changing anything in ODBC.

I think I answered my own question:

that is, that the place in ODBC where one enters "sa" and the sa password is just for allowing one to set ADDITIONAL SQL Server configuration items... not really just to allow an ODBC connection...

So we CAN just change the sa password in SQL Server without having to worry about changing everybody's ODBC, right?


Sound right?

 

[jazgeek]

sa/password on odbc is just used to set the connection up. Dynamics passes the actual login user/pass through to the sql server via odbc for actual authentication.

too bad it didn't do with your nt username......



-----------
and they wonder why they call it Great Pains!

jaz

 

[winthropdc]

Using the option in the ODBC to enter the sa password is just to allow any extra settings (which there aren't any) to be loaded and to be able to test the connection. The details are not stored. Changing the 'sa' password should not affect any normal users.

I am assuming that any VBA code that using ADO to access the SQL Server is RetrieveGlobals.dll to obtain the login credentials and is not hard coded to use to the 'sa' login and password.

David Musgrave [MSFT]
Senior Development Consultant
Escalation Engineer
MBS Support - Asia Pacific

Microsoft Business Solutions

http://www.microsoft.com/BusinessSolutions

Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.
This posting is provided "AS IS" with no warranties,
and confers no rights.

 

[35mph]

jazgeek, thanks for the info.

winthropdc, good point. We've got some modifed forms with VBA, but we haven't used ADO, and haven't referenced any logins or passwords anywhere in our VBA code, so I'm assuming we're ok on that point.

 

[35mph]

Incidentally, who's going to Microsoft Worldwide Partner Conference?