Skip to main content

I'm wondering how others go about managing FME's Database Connections in their environment.

Imagine you have hundreds of SQL Server databases. Most are named users... some are Windows Users.

Passwords are changed from time to time and this presents a problem for managing the named users.

One solution is to have one domain service account that can access all the different databases (on different servers, with different instances, and then the database specific permissions for this user). This is a heavy task for the DBA to set up but once it is set up, authentication from the FME engine takes care of itself and the FME admin doesn't have to manage the connections for the purpose of password changes.

The other way is for the FME Admin to manage the changing passwords inside of FME's Database Connections command. This is a daunting task when dealing with more than 200 databases.

Are there other ways you can think of to managed changing passwords related to named database users accounts?

Is this a pain point for others?

Be the first to reply!

Reply