11/25/2024 4:22:03 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss SQL Server or Oracle database administration related to SalesLogix databases. View the code of conduct for posting guidelines.
|
|
|
|
Remote sqlexpress sa passwords
Posted: 24 Oct 07 3:34 PM
|
OK, I'm leaning here, but I have a oracle db, sqlexpress on the admin workstation and sqexpress on the remotes.
Windows Policy requires strong password security and this means the sa passwords need to meet the strong password requirement for the sqlexpress servers (if all fails if you don't follow this)
So I create me db and install it on the remote. Life is good.
What is the sa password on the remote now?
-Its not what it was.
-Its not what what defined when I cut the remote.
-Clearly its not what is documented since documentation says it must be for oracle (apperenly they don't have a windows security policy in qa).
Surprisingly, sysdba is still the default handed fown from the public domain over a decade ago.
And yes, I can always manage sqlexpress if the remote user is a the local administrator.
|
|
|
|
Re: Remote sqlexpress sa passwords
Posted: 25 Oct 07 12:09 PM
|
Lane,
The SQL Server sa password will not pass down to the remote. The sa password on the remote is a seperate set of credentials. By default the sa password is blank for MSDE. If you want to set the sa password for a MSDE instance you can via command line on the box, so type the following:
osql -U sa (press ENTER twice)
sp_password @old = null, @new = 'NewPasswordHere', @loginame ='sa' (press ENTER)
go (press ENTER)
exit (press ENTER)
|
|
|
|
Re: Remote sqlexpress sa passwords
Posted: 26 Oct 07 7:56 AM
|
Actually, I preconfigured the sysdba and sa password's in sqlexpress prior to the attachremote process (sa blank, sysdba masterkey). Both were different than that those on the host. After the attachremote the sysdba remained unchanged while the sa WAS changed. But it wasn't changed to any of the 4 passwords I'd setup and verified prior to the process.
Also the C:\Documents and Settings\All Users\Application Data\SalesLogix\AttachRemote.ini file that was created originally was updated after the changes were pushed out. This references the Instance, sa user & password. It appears that everything will work fine since attachremote will now the sa pwd into the future. But as the sql administrator I'd like to know it too.
I'm doing some test to see if the behaior changes on mssql only systems or if the Windows Password complexity requirement goes away. |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|