Privileges for External DB ID with DevTest

Document ID : KB000093565
Last Modified Date : 30/04/2018
Show Technical Document Details
We are migrating to MS SQL DB from Derby and our DBA' s are provisioning 2 sets of ID's" Owner Accounts - these will be used for the initial setup to run the DDL commands. Once this is done, they want us to use APP account APP accounts- APP accounts will have the needed access (DML’s) Please advice if we need to have APP accounts to have DDL privileges or not.
All supported DevTest releases and platforms.
If you are allowing DevTest to create the tables on the SQL Server schema, then that user needs to have DBA authority.

When you start the Enterprise Dashboard and Registry, the user that is used to start the components needs to have DBA authority to create the tables.

Once the tables have been created, you can bring down the Enterprise Dashboard and Registry and then use another user that has all the authority to Create, Read, Update and Delete records from the database, without needing DBA authority.
Additional Information:
Please also refer to this documentation:

The schema is automatically created in the external database when the registry starts for the first time. Before the schema is created, ensure that the DevTest user has DBA privileges. After the schema is created, you can remove the DBA privileges from the user. If your security policy does not permit this approach, the database administrator can manually create the schema. The DDL files in the LISA_HOME\database directory contain SQL statements that can serve as the basis for manually creating the schema. Provide this information to the database administrator.