Configuration Database

The GPV relies on a configuration database to manage the functions and behaviors of the web mapping application. This page documents the process from creating the configuration database. The configuration [database schema] (Database Schema) contains descriptions of the tables and columns.

This page described the steps required to install the configuration database.

Please note that the SQL scripts contain a version number within the name. For example, in the table creation script, GPV31_SQLServer_Create.sql, the "GPV31" indicates that the script was written for the 3.1 release. Not all versions of the GPV contain changes to the database schema. The GPV31 scripts will build the proper configuration schema for GPV versions 3.1 through 4.0.

GPV Prefix

Before you run the following scripts, you have the option to change the prefix of the tables that are going to install by changing the "set @prefix=" value in each of the scripts before running them. The create table script will combine the prefix value with the table name (e.g. GPV31Application) for all tables installed. The default is set to the version of the GPV that you are configuring.

• Unzip the latest [Database Configuration Scripts] (https://github.com/AppGeo/GPV/tree/master/SQLScripts) for your RDBMS (Oracle or SQL Server) to a location where you can access them from a SQL command line interface.

• Open a SQL command line (SQL Server Management Studio or Oracle's SQL*Plus)

• Navigate to the Database/Schema where you plan to set up your GPV configuration tables.

• Open each of the following script files, change the "set @prefix=" value, if desired, and then execute the scripts in order.

  1. SQLServer_Create.sql - creates configuration tables
  2. SQLServer_AddConstraints - add database integrity constraints to the configuration database
  3. SQLServer_LoadMailingLabels - Inserts standard mailing label definitions into the MailingLabel table
  4. SQLServer_InsertPrintTemplate - Inserts default print template definitions into the PrintTemplate and PrintTemplateContent tables