Share via

SQL Server Workflow Databases

  • Article

The Workflow Designer primarily uses two databases in Microsoft® SQL Server™ for the storage and retrieval of workflow information for each application:

  • The modSystem database, which stores the tables and information to support all workflow applications. If you are using Named Instances, each instance will have its own modSystem database to manage workflow applications on that instance.
  • Your workflow-enabled database, which stores information about the specific workflow application created for it. The objects added to your database include the tables, views, and stored procedures required to run the workflow application.

In addition, the Workflow Designer uses several extended stored procedures that were added to the Master database during installation.

**Caution   **You should not directly modify any tables in the modSystem database, because you can break the current functionality in the workflow application and impair forward compatibility with future versions of Microsoft® Office XP Developer. The Workflow Designer handles maintenance of the modSystem database. In addition, you should not modify any of the objects that the Workflow Designer creates in your workflow-enabled databases.

The modSystem Database

Each installation of Workflow Designer server components includes a single SQL Server database that acts as the registry for all the workflow applications on the server. This database, named modSystem, is a repository for templates and other internal components, such as the workflow application User Directory, and for metadata about all workflow applications created on the server. The modSystem tables are maintained by the Workflow Designer, so when changes are made to a workflow application, the modSystem tables are updated accordingly.

The Workflow-Enabled Database

A workflow application includes a SQL Server database containing objects, such as tables, stored procedures, and views that were created for the business process, as well as the database objects created by the Workflow Designer to enforce rules and events on data processing. The objects in a workflow-enabled database fall into two categories: internal workflow objects and user-defined objects.

  • Internal workflow objects   store information about the schema or structure of the workflow application. This includes information about the database tables used by the application and the relationships between columns in those tables.
  • User-defined objects   are defined by the database developer and are organized hierarchically. Every workflow application has at least one main user table that is the top-level or root of the hierarchy. In addition, a workflow application might have one or more detail tables and lookup tables that contain related information. For example, an Issue Tracking application might have a main table that stores issues, a detail table that stores multiple comments related to each issue, and a lookup table that stores a list of countries where issues might have originated. Most simple applications have only a single main user table, however more complex applications might require two or more main tables and numerous detail and lookup tables.

See Also

Workflow Applications Architecture for SQL Server | Workflow Applications | Workflow Web Sites | Workflow Templates | System Database Tables