×

Have You Seen Workflow Lately? Click here to check out all the new features in the latest version.

Supercharge your GE solution! Download a free trial of Proficy Operations Hub, CSense analytics, and more. Learn more about the Proficy 2024 releases, by signing up for one of our upcoming events.

Home
Get Started
Get Started Guide
Pre-Installation Consideration
Enable Connection between Workflow and SQL Server
In order for Workflow to connect to any edition of Microsoft^® SQL Server 2012 or later, you must configure SQL Server to enable the db_owner role on the SOADB database for the applicable login account.

Workflow Products Documentation

Get Started
- Get Started Guide
  - Installation Requirements
  - Pre-Installation Consideration
    - Architecture Considerations
      If you are installing an application server or extension server (that is, Workflow or User) on a 64-bit computer, you can configure the server for either 32-bit or 64-bit operation.
    - Prerequisites for Windows 2012 R2 Installations
    - Configure Windows Authentication for Workflow
      You can configure Workflow to use Windows authentication to connect to a remote SQL Server instance.
    - Windows Services for Workflow
      There are several Windows services that must be running in order for Workflow to function properly.
    - Security Certificates
    - Firewall Ports
      During server installations, the installation setup detects whether there is a firewall on the computer. You must either disable the firewall or configure it to allow communication with remote clients.
    - Database Backup and Restore
      Workflow utilizes SQL Server to store information. In order to ensure that the integrity of the information is maintained, it is important to back up your database on a regular basis.
    - Multiple Servers
      Workflow provides the ability to install across multiple servers, each of which hosts a set of services. A multi-server environment is transparent and appears to be a single server to remote clients.
    - Server Clustering and Failover
      Workflow provides the ability to implement Microsoft^® Windows Clustering, which allows you to configure your server environment to be fault tolerant.
    - Enable Connection between Workflow and SQL Server
      In order for Workflow to connect to any edition of Microsoft^® SQL Server 2012 or later, you must configure SQL Server to enable the db_owner role on the SOADB database for the applicable login account.
    - License Management
      The GE License Client provides a single, easy-to-use tool to both view and manage online software licensing.
    - Performance Counters
  - Installation Procedures
  - Server Clustering Implementation
  - Deploy the Web Task List
  - Log On Overview
  - Post-Installation Configuration
  - Upgrade Workflow
  - Install a Reporting Database
  - Terminal Server
  - ActiveX Task Controls
  - Workflow Task Client
  - Installation Security

Enable Connection between Workflow and SQL Server

In order for Workflow to connect to any edition of Microsoft^® SQL Server 2012 or later, you must configure SQL Server to enable the db_owner role on the SOADB database for the applicable login account.

If you are using Windows authentication for Workflow, the default login account is NT AUTHORITY\SYSTEM, which is predefined in SQL Server.

For increased security when using Windows authentication, you can modify the properties for the Workflow Server service after installing Workflow, to define a custom login name and credentials. (For more information, see Microsoft^® Windows help.) Another alternative is to select SQL Server authentication when installing Workflow. In either of these scenarios, you must add the user-specified login account to SQL Server, and then enable the db_owner role for that account.

For information on adding a login account to SQL Server, mapping a login to a database, and setting database roles, see the Microsoft^® SQL Server help.