SQL Database Setup Overview

Connect Daily uses a SQL database to hold the calendar data. This section covers how to create the database to hold the calendar data. Generally, these instructions are for your database administrator to follow.

Schema creation files are located in the cdaily-3.4.16/WEB-INF/sql directory. Use the calschema.sql file for your database engine.

The basic steps for all databases are:

1. Create the user account for the database if necessary.
2. Create the database. Select a character set/collation sequence that will be compatible with your installation. If in doubt, and your database supports it, UTF-8 or Unicode-16 is the best choice.
3. Grant the user appropriate rights in the database.
4. Login as the User and connect to the Calendar database.
5. Run the schema creation script.
6. Install the JDBC Drivers. If you are installing on an existing application server, this is probably done already. If you are installing a new servlet engine, the easiest thing to do is place the JDBC JAR files in the cdaily-3.4.16/WEB-INF/lib directory.
7. Edit configuration.properties and enter the JDBC connection settings for your database.
8. Configure the database backup routine.

Note The schema create script contains all commands necessary to drop existing tables and reload the schema. It is normal for error messages to appear at the beginning of the script stating that tables or views were not found to drop.

Caution

The schema script contains commands to drop all tables and re-create them. If you run this script on a production system, you will lose all data.

Enterprise Installation

If you will be creating multiple installations, it is possible to create one physical database and partition it into multiple logical databases. For example, you plan to implement the calendar software for 12 distinct sites. Since each site has unique facilities and needs, you would like the data to be logically separated. If your database engine supports per user table spaces, you can create one physical database and then create 12 users, one for each logical calendar. You would then login to the physical database as each distinct User and create the table structures. Finally, for each logical calendar you would specify the unique login for that site in the configuration.properties file.

For information on whether your database engine supports per-user table spaces, contact your SQL database vendor.