Follow-On Topics

Related Topics

# Technical Summary

## Working with other Tools

The Microsoft SQL Server Trigger tool independent of any other steps used in a task. However, it exposes parameters that may be mapped to task variables — these can be used by any other step.

### Objects Consumed

The Microsoft SQL Server Trigger Step does not consume any King Task Centre objects.

### Objects Exposed

Objects that the Microsoft SQL Server Trigger Step exposes that can be utilised by other Steps are listed below.

|  | Variables (Text) — Textual data is mapped to selected Parameter Variables for use in other Steps.

## Dependencies

The products, technologies, protocols or systems that are required for the Microsoft SQL Server Trigger Step to work are listed below.

|  | Microsoft SQL Server 2000 or higher — These versions support the use of triggers.

For a detailed description of supported SQL Server versions, go to King Task Centre Database.

Note that the account under which the SQL Server 2005 service runs, normally `NT AUTHORITY\NetworkService`, must not have restricted access to create COM objects or the trigger will fail with Access Denied. This can be resolved by granting the `NETWORK SERVICE` account launch permissions for the SQL Agent COM Component:

1. Run `dcomcnfg`
2. Locate the `iwsqlea` object in the DCOM Config branch under Component Services
3. Edit the Launch and Activation Permissions under the Security Tab of the `iwsqlea` properties
4. Add `NETWORK SERVICES` user, and allow them Local Launch and Local Activation rights

|  | ODBC Compliant Data Source

|  | Microsoft SQL Server Trigger Agent — The agent must be installed on the SQL Server.

Copyright © 2018 Quadrant Software B.V. All rights reserved.