Setting Up a Table Hierarchy

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 uses a hierarchy of tables to manage core features and services in a workflow-enabled database. The hierarchy consists of main, detail, and lookup tables. This hierarchical structure makes it possible for detail and lookup tables to inherit permissions and properties from the parent main table.

The hierarchy is displayed under the Tables folder of the Solution Explorer in the Workflow Designer for SQL Server. When you designate a table as a main table, all tables that have primary key or foreign key relationships with it also are included in the table hierarchy as either detail or lookup tables.

When you add a main table to the hierarchy, the Workflow Designer creates a view of the main table and sets access permissions for the Public role. Public permissions are required for data access page interaction.

When you add workflow to your application, Workflow Designer for SQL Server creates lookup tables that support the workflow and adds them to the table hierarchy. For example, when you add workflow to a table, a <*tablename>*StateLookup table is created and displayed in the Solution Explorer.

See Also

Building Workflow Applications for SQL Server | Understanding the Workflow Application | Creating Workflow Applications from Databases | Understanding the Workflow Process | Defining Hierarchy Schema | Defining Table Security