Create a database

​

Create a new database

1

Install the database client driver

On the computer where the Application Server is installed, install one of the following client drivers:

• Microsoft SQL Server Native Client 2012 or later
• Oracle Data Access Components (ODAC) of the same bitness as the Application Server
• psqlODBC version 11 or later

If you attempt to create a database without Microsoft SQL Server Native Client, you see this error message: Provider cannot be found. It may not be properly installed.

You don’t need to install Microsoft SQL Server Native Client if you have Microsoft SQL Server 2016 SP2 or later, or Microsoft SQL Management Studio 2016 SP2 or later, installed.

2

Open the Administration and Monitoring Console

On the computer where the Application Server is installed, sign in with the Windows administrator account. Open the Administration and Monitoring Console and click Service → Application Server to open the page https://<ApplicationServer>/FlexiCapture12/Monitoring/#Settings/DbConn, where <ApplicationServer> is the name of the computer that hosts the Application Server.

If you are already connected to another database, close the existing sessions before creating a new database. If that is not possible or necessary, add the following key to the web.config file located at <IIS Root Directory>\FlexiCapture12\Monitoring (the default IIS root location is C:\inetpub\wwwroot):

<appSettings>
<add key="IgnoreCurrentSessions" value="true"/>
</appSettings>

The new database is then created without a warning about existing sessions, and all sessions in the old database are preserved. By default, the key is set to false and you are prompted to close the sessions when creating a new database.

3

Specify the connection settings

Click the Create New Database button. On the database creation page that opens, specify:

• The server instance name, in the format <server name>\<instance name>.
• The name of the new database.
• A user account with the necessary permissions for your database.

Choose the TCP/IP protocol rather than Named Pipes to communicate with the database server. You set the protocol when you configure the Microsoft SQL Server client on the computer that hosts the Application Server.Select your database type for its screenshot and specific requirements:

• Microsoft SQL Server
• Oracle
• Azure
• PostgreSQL

Note the limitations that Microsoft SQL Server imposes on database names. For more information, see this Microsoft website.

The connecting user must have the “DBA” WITH ADMIN OPTION role and the EXECUTE privilege on “SYS”.”DBMS_LOCK”. Note the Oracle restrictions on user names. For more information, see the Oracle website.

To create a PostgreSQL database, the user needs the CREATEDB+CREATEROLE or SUPERUSER role attributes. A user account with the necessary permissions is created automatically, named in the FCUser12_DatabaseName format (where DatabaseName is the name of the database).

4

Set up file storage

Select the Use external file storage option and specify the path to the file storage. The file storage holds binary data such as document images, project settings, and captured data.For best performance, place the file storage on the same disk as the Application Server. In enterprise environments, use a fail-safe disk, RAID, or high-performance external storage. Add the file storage to the exceptions of your antivirus software and the Windows Search indexer.For more information, including how to run without a file storage, see Set up a file storage.

5

Test the connection

Use the Test Connection button to check the entered values. If the test is successful, click OK.If you encounter authentication problems when testing the connection, make sure that Mixed Authentication Mode (“SQL Server and Windows authentication”) is enabled for Microsoft SQL Server.

​

After you create the database

• Change the Application Server settings
• Upload projects
• Grant access permissions for projects
• Create users and manage their roles and permissions
• Grant the Administrator role to another user and delegate further configuration of the system

​

What happens when the database is created

1. A FlexiCapture 12 database is created. The account used depends on the authentication method:
   • Server authentication – the account specified on the Settings → Application Server → Connect to Existing Database / Create New Database page.
   • Windows authentication – the account under which the browser displaying the Application Server runs.
   This account runs Description.sql, which creates the database, and then DBInitFill.sql, which populates it with data. Both scripts are in <IIS Root Directory>\FlexiCapture12\Server (the default is C:\inetpub\wwwroot). The Upgrade*.sql files in the same folder are not used for database creation.
2. A Database Server account is added. This is the account under which the FlexiCapture 12 Web Services application pool runs on the Application Server (Network Service by default).
3. The step 2 account is granted db_owner permissions on the FlexiCapture12 database from step 1. The Application Server uses the step 2 account for all further interaction with the database, so you can delete the step 1 account if it is no longer needed.

​

Database permissions and privileges

​

Microsoft SQL Server

• CREATE ANY DATABASE (required to create a new database)
• SECURITYADMIN (required to create a new user under whose account the Application Server is running)

• EXECUTE ON SCHEMA::DBO
• SELECT ON SCHEMA::DBO

• DB_DATAREADER
• DB_DATAWRITER (DBInitFill)
• DB_DDLADMIN
• ALTER ON DATABASE::<DB_NAME> (required for specifying the recovery model and enabling Snapshot isolation)
• EXECUTE ON SCHEMA::DBO
• GRANT EXECUTE ON SCHEMA::DBO
• DB_BACKUPOPERATOR (required for creating backups and restoring the database)
• DB_ACCESSADMIN (required for adding users to the database)
• DB_SECURITYADMIN (required for managing database permissions)

​

Oracle

• CONNECT
• CREATE SESSION
• CREATE TABLE
• CREATE VIEW
• CREATE SEQUENCE
• CREATE PROCEDURE
• CREATE TYPE
• CREATE TRIGGER
• EXECUTE ON SYS.DBMS_LOCK

​

PostgreSQL

• CREATEDB+CREATEROLE
• SUPERUSER