contentACCESS Email Archive – Best Practices version Hector

5.Creating a database to the tenant

Open page All databases (System => Tenants => All databases), click + create new and specify the required values in the Database repository window. Create a single SQL database to TECH-ARROW tenant with connection name “Email Archive DB” and Database user “Administrator”. We won’t use the system database server (TACATEST) as it is recommended to use a separate one, so we leave the “Use system database server (TACATEST)” checkbox unchecked. The application will automatically set this first created database to default.

Configuration details

Connection name: the display name of the database in contentACCESS
Option “Use system database server”: if the database must be created on the system database server, select this option; otherwise, specify the required database values (Server name, Database, Schema) manually.

In section Database user, you need to specify a user for the newly created database:
Enter the credentials of the existing MSSQL user or create a new user and password, clicking on the Generate user and password button. contentACCESS will give access rights to the database on MSSQL for this user. This newly created user will have access permissions only to the created database. If you specify no explicit user in this section, then the service user will be used to access the database.

In section Connect with user, you must specify the MSSQL admin credentials:
Use explicit credentials: if this checkbox is not checked, then contentACCESS will automatically connect to the database (MSSQL) under the contentACCESS service account. If you wish to connect with an explicit user, then specify an admin user with the rights to create a new database on the database server.
Tenants: select the database owner tenant from the dropdown list (in our case TECH-ARROW).

Note: When creating databases, always consider the size of the company and the number of mailboxes archived. For bigger companies with a high number of mailboxes (more than 2,000), it is always recommended to create separate databases, e.g., one for the store and one for the email archive to ensure the transparency of processes. The database created at first will be the default database. This option is configurable on the page of Databases using the context menu.
Yes No Suggest edit
Help Guide Powered by Documentor
Suggest Edit