SQL application definition

This section describes the files that application Developers must use to define their Relational Database Management System (RDBMS)- resident application pieces for the OASyS DNA SQL Installation Tool.

In order to understand the behavior of the OASyS DNA SQL Installation Tool, it is necessary to explain how the AVEVA Enterprise SCADA environment organizes the RDBMS-resident application pieces.

In general, application components that reside in the RDBMS are one of the following:

• Schema definition (tables, indexes, etc.).

• Views and other Administrator-visible presentations of the schema.

• Stored procedures.

• Raw data that is used to initialize the application tables.

For a reasonably complex application, break up these aspects of the application into individual Microsoft SQL files. A construct called the applications sequence file (*.seq) is provided to allow Developers to specify the order in which individual files are loaded. This file is an ordered list of the Microsoft SQL files that describe the application.

Dependencies may exist between applications. This means that there is an order in which applications must be loaded into the RDBMS. The application suite file (*.ste) is an ordered list that specifies the order in which individual applications are installed.

The OASyS DNA SQL Installation Tool reads and uses the applications sequence and application suite files to construct the tree view that is shown on the Application Table Configuration Files tab.

There are two levels of application grouping that you must provide. One is applications sequence, which defines the order of loading of the Microsoft SQL scripts that define an application. The other is the application suite, which defines an application with respect to the other applications on which it depends.