enrique_aeo
asked on
hange the password - SQL Server level main login
I need to change the password of a user at SQL Server level (main login of systems).
But my doubt is that other things I should check before making this change, that other factors can be affected by doing this since this user used it almost for everything within this DB.
Obvious that at the application level will make the respective changes with the new password (it is a production pass-through server, nobody has access to this), but my doubt comes from things in the database itself, for example, as the Replicas that I have to other servers, sending mails, or where else should I look where maybe that password is left and I have to update it for the new one perhaps manually.
Here are several servers, I have to check all and see which are connected to my main server, since changing the password will cause several (load processes, dblinks, etc) to fall.
What is the correct way to make this change to decrease the margin of error
But my doubt is that other things I should check before making this change, that other factors can be affected by doing this since this user used it almost for everything within this DB.
Obvious that at the application level will make the respective changes with the new password (it is a production pass-through server, nobody has access to this), but my doubt comes from things in the database itself, for example, as the Replicas that I have to other servers, sending mails, or where else should I look where maybe that password is left and I have to update it for the new one perhaps manually.
Here are several servers, I have to check all and see which are connected to my main server, since changing the password will cause several (load processes, dblinks, etc) to fall.
What is the correct way to make this change to decrease the margin of error
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
What happens is that there are several servers (there is no documentation of that) that connect ETL, DBLInks, Replicas, etc. with the main server, then if the user changes the entire DB will be affected.
Is there a way to validate some points before making the change?
What do you recomend?