Configuring SQL Server Profiler for Performance Related Issues
Issue
When encountering any performance related issues with Kofax Capture, Kofax Technical Support may request that a SQL Server Profiler trace be captured while reproducing the issue.
Solution
Below are the steps required to configure SQL Server Profiler to capture the correct events for the trace. Be sure that the SQL account has the proper rights to the Capture database to configure and capture all events.
1. Before selecting any events, enable “Show all events” and “Show all columns” options.
NOTE: It is important to note that events can be fully or partially enabled.
When fully enabled, this means that all columns for the event will be traced and the check mark is clear. For all items in this document, make sure that the check marks are clear.
When an event contains some selected columns, a lighter check mark is used.
2. Locks – select Deadlock Graph, Lock:Deadlock and LockDeadlock Chain (all columns for each)
3. Stored Procedures – RPC Starting and Completed events (all columns).
4. TSQL – SQL:BatchStarting and SQL:BatchCompleted events ( all columns).
Filters:
1. ApplicationName is usually enabled by default - this is OK.
2. Add the following to filter only from the KC production database (actual DB name referenced here):
3. Verify that no other filters exist.
Level of Complexity
Moderate
Applies to
| Product | Version | Build | Environment | Hardware |
|---|---|---|---|---|
| Kofax Capture |
11.0 11.1 |
Article # 3032693