1. From the main Navigation Menu, select Data Sources > Realtime Triggers.
   

   

2. On the Realtime Triggers page, click the Create Realtime Trigger Button.
   

   

3. On the New Realtime Trigger page, click MSSQL Table Real-Time Data Source.
   

   

4. The page to configure the MSSQL Realtime Data Source opens.

Data Source Setup

5. Description – a friendly description for the MSSQL Table Real-Time Data Source.
6. Connection – Select the MSSQL connection to be used from the dropdown list.
7. Database– Select the Database containing the table to track
8. Table – Select the Table to track.
9. Restrict Table Columns – If you only want to trigger the source on certain columns, mark those here.
10. Click Validate.
11. Log Action – Set the Log action as needed.
    • Save Failures: Will log only failed records.
    • Always Save: Will log successes and failures.
    • Save Successes: Will log only successes.
    • None: will not log any records.
12. Click Save.

Trigger Configuration

You can expand the Trigger Configuration section to modify the SQL trigger behavior. Enabling a local queue is advised when auditing and greater integration resilience is required.

1. Enable Local Queue– Should web request calls be logged on client SQL server.
   • Enabled – logging table (eOneQueue_WebRequests) will be created on the client SQL server database where calls to the realtime service will be logged. It will also create a SQL Server Job pointing to that database that will attempt to retry records if initial processing fails, as well as a job to purge processed records.
   • Disabled -Realtime records will not be logged on the client SQL server and will only be logged in SmartConnect.
2. Retry Interval (seconds) – If the SQL server tries to connect to the realtime service, and fails, this is the default time before it attempts to connect again.
3. Increase Retry Interval With Each Attempt – reduce service overhead
   • Enabled – Each failed attempt will cause the retry interval to be extended. Retry interval will be the base retry interval multiplied by the number of failed attempts.
   • Disabled – Each retry will occur on the Retry Interval defined above.
4. Maximum Retry Minutes – This is the time after with processing retries will cease.
5. Record Successes – Determines which records are logged on client SQL server.
   • Enabled – All triggered calls will be logged
   • Disabled – Only failed web requests from trigger calls will be logged
6. Purge After Hours – Number of hours before records are removed from the logging table.