Create a Subscriptions Database

The document event subscription feature requires an existing external database in which to store subscription information for each user. By default, Meridian Enterprise does not create this database automatically. If subscriptions will be allowed in the vault, a database must be created by a database administrator. The Meridian application server and the database must meet the requirements described in Meridian Application Server Requirements. Scripts for SQL Server and Oracle are installed by the Meridian Enterprise setup program for your convenience that will create the database and the necessary schema. The scripts must be executed by a user with sufficient rights to perform the actions in the scripts.

Once you have created your subscriptions database, you will need to connect it to your vault using the Notifications table connection string setting.

Important!

If the subscription database already exists, the scripts will delete it first and then recreate it.

SQL Server

To create a subscriptions database in SQL Server:

Copy the following script file from the Meridian application server to the SQL Server host computer:
```
C:\Program Files\BC-Meridian\Program\BC Notification\BCNotesDB.sql
```
On the SQL Server host computer, navigate to the folder where you copied the file in step 1.
Run the script using the sqlcmd command-line program and one of the following examples:
Note:
- We recommend using the database name <VaultName>Subscriptions.
- If the database server is running SQL Server Express, SQL Server Small Business, or another edition that creates a default named instance when the software is installed, specify the name of the database server and the SQL Server instance name together, for example, <ServerName>\SQLEXPRESS or <ServerName>\MSSMLBIZ.
```
sqlcmd -S <ServerName> -E -i BCNotesDB.sql -v DatabaseName = "<SubscriptionsDatabaseName>"
```
OR
```
sqlcmd -S <ServerName> -U <UserName> -P <Password> -i BCNotesDB.sql -v DatabaseName = "<SubscriptionsDatabaseName>"
```