Planning Workflow Applications for SQL Server

Planning is the key to developing successful workflow applications. Naturally, the database that stores the items to which you want to apply workflow is the centerpiece of your plan. This topic assumes you have created a database already and you are ready to add workflow to it. Based on the function of the database, you can identify the states that each item must pass through and the states that an item might pass through optionally or conditionally. Using the Workflow Designer for SQL Server, you can script events to control how items move from state to state through the workflow process.

In addition to the workflow process, you must develop a user interface and determine the various roles the application must have to control user interaction with data and database objects.

Workflow applications depend on the security and permissions provided by Microsoft® SQL Server™ and the operating system; these permissions and privileges must be reviewed carefully before beginning application development.

In This Section

  • Workflow Application Development Guidelines
    Review the design considerations for the database schema, scripting, and other aspects affecting a workflow application.
  • Security Permissions Model
    Workflow Designer for SQL Server leverages Microsoft® Windows® 2000 and Microsoft® SQL Server™ security for its own security model. You can manage users and groups through the Windows 2000 Active Directory.
  • Database Tools and Technologies
    Consider the features and capabilities of database tools Microsoft® Jet, Microsoft® SQL Server™ 2000 Desktop Engine, and Microsoft® SQL Server™.
  • The Workflow Engine Model
    Understand how the workflow engine enforces the workflow process definition and executes workflow events.