SQL Profiler can be used to determine whether or not TIBCO Scribe® Insight
is sending data to the target as it is mapped in the DTS. The target API may follow different rules than what you expect, and what Scribe sends may not be what is written to the target.
This article provides an example of troubleshooting steps using SQL Profiler that help you isolate the cause of the mapping problem into the Dynamics GP target database. In this example, the DTS mapped a specific field value (checkbook ID), but the value was not written as expected to the Dynamics GP database. With the SQL Profiler trace, you can see Scribe sent the mapped value, but the result was different when the transaction was written to GP. When the target API changes the value you mapped in the DTS, you need to look at the target application rules to understand why the target application overrode the value. In this Dynamics GP example, the checkbook ID needed to be set at the batch level and not the transaction level.
Using SQL Profiler
Requires SQL Management Studio. This tool is not available with SQL Express.
- Open SQL Management Studio and select Tools > SQL Server Profiler.
- In Trace Properties on the General tab, enter a trace name.
- Click on the Events Selection tab
- On the Events Selection tab, uncheck Audit Login and Audit Logout, and check Show all columns.
- Check all boxes in the DatabaseName column and click the Column Filters button.
- Select DatabaseName, Expand Like, and enter the Database name for the filter, such as, a GP company DB.
- Click OK.
- At the bottom of the Trace Properties dialog, click the Run button.
- Run the TIBCO Scribe® Insight process you want to monitor, such as a TIBCO Scribe® Insight DTS.
- Search the SQL trace that is generated for a stored procedure name or table name or some other identifying data to locate a record with the problem data.
For additional information, see the following in the TIBCO Scribe® Insight Help:
Trace Files,
Application Options – Tracing Tab,
Logging Tab