When a Data Admin is editing a query in a Data Configuration, that Data Admin will see databases on the server according to the permissions in the Database Connection.
If the Data Admins are not authorized to see all the databases on the server, then a more restrictive permissions set must be used in the Database Connection.
For example:
User "FrenchUser", who has permissions to only the database of interest, named "ProductionExamples":
In Enterprise Manager, users "Bill" and "Mary" are created who have Database Admin permissions:
When Bill logs in to Enterprise Manager, Bill only sees the Database Connection objects. Bill creates a new Database Connection, and uses the database server user permissions of FrenchUser:
Then Bill gives Mary “Read” but not “Edit” permissions to the Database Connection:
When Mary logs in to Enterprise Manager, she will only be able to create Data Configurations:
When Mary creates a Data Configuration, she will only see the Database Connections for which she has “Read” permissions:
When Mary edits a query in the Data Configuration, she will only see those databases for which the underlying Database Connection has permissions (controlled by FrenchUser permissions). In other words, the permissions in the Database Connection control which databases Mary can see on the server:
Since FrenchUser on the database server only had permissions to the ProductionExamples database, and FrenchUser was used in the Database Connection, then any Data Configuration based on that Database Connection will only see the databases on SQL Server that FrenchUser has permissions for.