Creating a Database

Before you create a Database connector, you must create a database with a table to store message data. This table must include the MessageContents The MessageContents field stores the message in the database in a ZIP file. The field type must be IMAGE (for a SQL database) for the connector to be able to store the message. The MessageContents field is only required if you are storing the files directly into the database. It is not required if you are storing the documents in a folder share. and MessageBodyPath The MessageBodyPath field stores a path to a location on a system in the network where the Database connector has stored the file. The field that you use for this field name must be of type MEMO so that there is no length restriction. required fields.

To create a database for the Database connector

1. Create a SQL database.

2. Create a table in the database where you want to store the message data.

3. Add the following required fields to the table.

   • MessageContents
   • MessageBodyPath

Note:  Ensure the field names are spelled correctly. No data is recorded if the field names are inaccurate.

4. Save and close the database.

Database connection string guidelines

You can use the following guidelines to create a connection string for your database.

• Create the connection string using the following format.

keyword=value;keyword=value;keyword=value

• Use appropriate keywords for the type of database you will use. See the examples listed below.

Examples of SQL database connection strings

In most cases, the server will connect to your SQL database using a trusted connection. However, if you modify this setting so that the server connects to your SQL database through SQL security protocol, you need to create your connection string using a different format.

SQL database using a trusted connection (default)

For a trusted connection, the connection string should contain the provider, data source, initial catalog, and integrated security settings. This information tells the server the type of database you are using, the location of the database, the name of the database, and the method for connecting to this database.

The following string shows you the general format you should use when you create a connection string for a trusted connection.

Provider=sqloledb;Data Source=ServerName;Initial Catalog=DatabaseName;Integrated Security=SSPI

This is an actual example of a connection string for a trusted connection.

Provider=sqloledb;Data Source=Mercury;Initial Catalog=FaxArchive;Integrated Security=SSPI

SQL database using SQL security

For SQL security, the connection string should contain the provider, data source, initial catalog, user name, and password. This information tells the server the type of database you are using, the location of the database, the name of the database, and the username and password of the user account.

Note: The user name and password are required so that the Upland AccuRoute Server can gain access to the database.

The following string shows you the general format you should use when you create a connection string if you have enabled SQL security.

Provider=sqloledb;Data Source=ServerName;Initial Catalog=DatabaseName;User Id=Username;Password=Password

This string shows you an actual example of a connection string that you might use if you enabled SQL security.

Provider=sqloledb;Data Source=Mercury;Initial Catalog=FaxArchive;User Id=IT_Administrator;Password=7h3k62br

See also

About Database Connector

Database Connector Requirements

Adding a Database Connector

Database Connector Fields List