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!
|
|
Changing the sysdba password
Posted: 11 Jul 07 6:44 PM
|
We have a client who insists on changing the sysdba password. My question is: Are there any really bad implications to doing this?
From what I know, I'd have to change the password in SQL Server for the sysdba login and edit the low level connection via Connection Manager. This client doesn't have any Remote Users yet and I know that Remote databases would have to be re-made. I thinking that once the low level OLE-DB connection is reset via Connection Manager, the client level connections would not have to be changed. Is this correct?
|
|
|
|
Re: Changing the sysdba password
Posted: 11 Jul 07 6:59 PM
|
You are correct about the client connections ... no change needed.
I have seen cases where developers need to create a pure SQL connection to the db in code (ie bypassing the OLEDB Provider) - usually to run complex SELECT queries that the provider cannot parse. In these cases, the standard SYSDBA password is sometimes hard-coded into the scripts to create the db connection. Nasty, but true. So at least consider the possibility of this.
Have you any external applications that connect directly to the db? Eg DTS scripts? They may need to be looked at. |
|
|
|
Re: Changing the sysdba password
Posted: 12 Jul 07 3:45 AM
|
We changed our sysdba password. From a saleslogix point of view everything worked OK after that, however we had an issue with a data synchronization program where the developers had hardcode the password into the application.
Essentially there should be no issues with changing the sysdba password, and it should be something everyone does out of the box, in my opinion. Knowing that anyone who has access to my network can get access to a SQL server by using sysdba and masterkey is discomforting to say the least. As I mentioned, the only issues changing the password caused for us had to do with numpty developers hardcoding the sysdba password into their application. I would spend a bit of time researching any external apps or procedures which might have the sysdba password hardcoded so that those issues can be corrected before going live with the password change.
|
|
|
|
Re: Changing the sysdba password
Posted: 12 Jul 07 7:31 AM
|
I believe you are also going to have to stop the Synchronization Server (if you have one running) and change the sysdba password there (I think there is a separate are for that) then restart the sync server.
John G. |
|
|
|
Re: Changing the sysdba password
Posted: 12 Jul 07 8:33 AM
|
Thanks all. You have confirmed what I was thinking plus some very good pointers regarding external apps. I already knew about re-initializing the Sync Server. I'm going to try it out on a test system first. Thanks again. |
|
|
|