OpCon Database Scripts
Theme: Configure
Who Is It For? System Administrator
What Is It?
Continuous provides several SQL scripts for installing and upgrading the OpCon database and supporting data. Scripts are located in the <Configuration Directory>\Utilities\Database\ directory.
The Configuration Directory location depends on where you installed your programs. For more information, refer to File Locations in the Concepts online help.
Log files generated by these scripts are written to the <Output Directory>\Utilities\Database\Log\ folder.
The Output Directory was configured during installation. For more information, refer to File Locations in the Concepts online help.
Database Creation Script
Script name: DB_Create.sql
- Creates a database called OPCONXPS in the SQL Server Data directory
- Allocates an initial 200 MB for the database
- Allocates an initial 1 GB for the transaction log
- Sets the database options
- Generates output to DB_Setup.log (creation) or DB_Update.log (update)
Logins and Roles Creation Script
Script name: CreateDefaultOpConxpsloginsAndRoles.sql
- Creates the opconsam and opconui login IDs
- Creates opconxps, opconreader, and opconspuser database roles
- Generates output to DB_Setup.log (creation) or DB_Update.log (update)
Schema Installation Script
Script name: Opconxps_DBTables.sql
- Installs or updates the OpCon database schema
- Grants full control to the "OpConxps" role for all OpCon tables
- Grants read-only access to the "opconreader" role for all OpCon tables
- Populates static tables with data
- Loads initial data to selected administration tables
- Generates output to DB_Setup.log (creation) or DB_Update.log (update)
Database Stored Procedures Script
Script name: OpConxps_DBProcs.sql
- Creates all stored procedures supporting OpCon features and processing
- Grants EXEC permissions on all stored procedures to the opconxps database role
- Grants EXEC permission for supplemental stored procedures to the "opconspuser" role
- Generates output to DB_Setup.log (creation) or DB_Update.log (update)
Database Functions Script
Script name: OpConxps_DBFunctions.sql
- Creates all database functions supporting OpCon features and processing
- Generates output to DB_Setup.log (creation) or DB_Update.log (update)
PDSA Framework Script
Script name: PDSAFramework.sql
- Creates tables required for the PDSA
- Grants full control to the "OpConxps" role for all PDSA tables
- Grants read-only access to the "opconreader" role for all PDSA tables
- Generates output to DB_Setup.log (creation) or DB_Update.log (update)
PDSA Framework Data Script
Script name: PDSAFrameworkData.sql
- Generates output to the
<Database Name>_PDSAData.logfile
Audit Triggers Script
Script name: OpConxps_DBTriggers.sql
- Creates INSERT, DELETE, and UPDATE triggers on a subset of OpCon database tables to record audit data
- Generates output to DB_Setup.log (creation) or DB_Update.log (update)
Pre Update Checks Script
Script name: PreUpdateChecks.sql
- Checks that the SQL Compatibility level matches the current SQL version; updates the value if too old
- Checks the History Archive table for duplicate records; deletes any duplicates found
- Creates a list of machines and machine groups with jobs (excluding OpenVMS, OS2200, MPE/ix, and BIS) where platform-specific job data is in legacy format
- Writes the list to the log file for user review
- Generates output to DB_Setup.log (creation) or DB_Update.log (update)
Configuration Options
| Setting | What It Does | Default | Notes |
|---|
FAQs
Q: Where are the OpCon database scripts located?
Database scripts are located in the <Configuration Directory>\Utilities\Database\ directory. Log files generated by the scripts are written to <Output Directory>\Utilities\Database\Log\.
Q: What does the Database Creation Script (DB_Create.sql) do?
It creates the OPCONXPS database in SQL Server, allocating an initial 200 MB for the database and 1 GB for the transaction log.
Q: Where can you find the scripts after an upgrade if they are no longer distributed as files?
Refer to the Innovation Lab on GitHub for instructions on manually migrating the scripts. On new installs, these are included as Embedded Scripts.
Glossary
OpConxps: The standard installation directory name for OpCon program files, configuration files, and output data on Windows machines.
Embedded Script: A script stored and versioned directly within the OpCon database. Embedded scripts can be assigned to Windows jobs and run at runtime without requiring the script file to exist on the target machine.
Audit Record: An automatically created log entry recording every change made to an OpCon object. Each record captures the timestamp, the user or application that made the change, the item affected, and the original and final values.
Role: A named security profile in OpCon that groups privileges together. Roles are assigned to user accounts to control which features, schedules, jobs, machines, and administrative functions a user can access.
Machine: A platform defined in the OpCon database that has an agent installed. OpCon routes job execution requests to machines via SMANetCom, and machines report job completion status back to SAM.
Job: The fundamental unit of work in OpCon. A job defines what to run, on which machine, when to start, and what conditions must be met. Job results are tracked and can trigger events and notifications.
OpCon: Continuous' workflow automation platform. The OpCon server includes the database, SAM and Supporting Services (SAM-SS), and graphical user interfaces. agents installed on target platforms run jobs and report results.