- Choose No when asked if the database is already configured and click Next
- Enter in the appropriate values for the connection to the database server and click Next
- Server: The URL for your SQL Server instance
- Authentication mode: SQL Server login uses a username and password, Integrated security uses the currently logged in user's AD privileges
- Database administrator: Username of the SQL Server account that has elevated privileges for creating/editing database
- Administrator password: Password for the above account
- The DB Admin Username and password are not stored anywhere within epiCentre and are only used for the initial setup process
- Enter in the appropriate details for the new database and click Next
- Server: Same as previous screen, and should be pre-filled
- Database: The name of the database you want to create (i.e. epiCentre)
- Authentication mode: SQL Server login uses a username and password, Integrated security uses the currently logged in user's AD privileges
- If you choose Integrated security, please be aware that this requires that all users of epiCentre have the same elevated privileges in SQL Server
- Username prefix: The prefix for the SQL Logins that will be created (i.e. epiCentre prefix means epiCentre_dbo, epiCentre_reader, epiCentre_user)
- Owner password: The password for the db_owner user account. Please enter the password in again in the second text box
- User password: The password for the db_datareader and db_datawriter user account. Please enter the password in again in the second text box
- Reader password: The password the db_datareader user account. Please enter the password in again in the second text box
- Database file path: This is the path for the actual database file. This path must be a directory that SQL Server has read/write privileges in.
- Encrypt connection: Tick this checkbox if you want to encrypt the connection to the database (i.e SSL)
- Trust server certificate: Only available if you ticked Encrypt connection; tick this checkbox if you want epiCentre to trust the certificate provided on the database server, without checking it against a signing authority
- Multi Subnet Failover: Tick this checkbox if your SQL Server is set up in a failover cluster configuration
- Additional connection properties: If you need more connection options that aren't provided, use this space to add whatever you need (i.e. Network Library=DBMSSOCN;MultipleActiveResultSets=true;)
- Enter the encryption key for your database and click Next
- The encryption key is not provided by ePPOC and should be decided upon by the service or IT, and noted somewhere where it won't be lost/deleted
- The encryption key is not provided by ePPOC and should be decided upon by the service or IT, and noted somewhere where it won't be lost/deleted
General
Content
Integrations