Share via

Workflow Application Infrastructure

  • Article

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

The Workflow Designer for SQL Server infrastructure supports the design-time and run-time features in a workflow application through stored procedures and extensions to database tables. Those extensions are the glue between the Workflow Designer, the client data access pages, and the workflow-enabled database.

The infrastructure is based primarily on the server, so users can use any client tool to leverage the stored procedures. The Workflow Designer creates a database called modSystem on SQL Server where information about all the workflow applications is stored. In addition, when workflow is enabled on a database the Workflow Designer adds a number of objects to that database, including tables, views, and stored procedures.

You are not required to know details of the infrastructure to use the Workflow Designer to create and modify your workflow applications. This information is provided for those who want to understand how the workflow application works behind the scenes.

See Also

SQL Server Workflow Reference | Workflow Scripting Reference | SQL Server Workflow Toolbar Control | ModHFGrid Control | ModSystem Database Tables | Workflow-Enabled Database Tables | Stored Procedures | Views