Answer the question
In order to leave comments, you need to log in
How to change the password on the DBMS without interrupting the client application?
Introductory:
Host 1. Application, login-password to the DBMS are stored locally. SLA 24/7.
Host 2. DBMS. It can be anything: from MongoDB to Sybase ASE.
Task:
Change the password for the DBMS login without interrupting the application.
Are there any effective ways, except for these:
1) synchronous password change (minimum downtime, but it exists);
2) creating a second login, switching the application to it, deactivating the first login (inconsistency from the point of view of documentary accounting: one login was approved, but in fact another one works).
Answer the question
In order to leave comments, you need to log in
On host1, one command (sed -i) changes the password in the settings file, and, separated by a semicolon (;), the second command (sql-client-tool <cmd.sql) sends instructions to the SQL server to change the password. The execution time is micro fractions of a second, you won’t have time to blink.
you need to look where and how your specific subd stores access settings and whether they can be changed without restarting the server.
in mysql, postgre does not need to be restarted - changed the password and did flush privileges.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question