Within the Reference Data Mgr menu in the left pane, click on Database to bring up the list of all databases that we have configured details for in emdash.
For a new environment, we want to create a new Database definition. Click on the Add Database button and you will be brought into the Create Database page.
The Endur application only has one database allocated to it – so fill in all of the fields as follows:
- Database Name – The name of the database. For Endur, this should be in the format END_<EnvironmentName>. E.g. for CP01, the Endur database is END_CP01.
- Server Name – The SQL instance where the Endur database will be located, e.g. ABCENDB01\ENDTEST01
- Database Type – Drop down list containing all permissible values for Database Type across all applications. For Endur, select ‘Endur’.
- DB Technology – Data to tell us what type of database it is. Endur is ‘SQL Server’.
- DB Technology Version – Data to tell us what version of SQL Server is running on the target SQL instance.
Now, log into SQL Management Studio onto the target SQL instance above, and create a new ‘shell’ database for the one defined above. The shell database can have its data and log file locations specified onto disks that have the appropriate amount of space. Emdash will preserve these disk locations through environment refreshes – but it is not able to move them around. Use SQL Management Studio or a DBA if that’s needed. Ideally you would put in a small Endur database by a manual backup.
Doing this will allow the UserAllocation process to work as without it the Add UserAllocation workflow jobs will fail as emdash will not be able to find the relevant Endur tables and stored procedures in the Endur database.