Skip to main content
Kofax

Configuring SQL Server Profiler for Performance Related Issues

Article # 3032693 - Page views: 157

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.

clipboard_e6661c6f04d435ec4b276f37a186cefa6.png

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.

clipboard_ec0091c565a0330e87d04bc8cbc148215.png

When an event contains some selected columns, a lighter check mark is used.

clipboard_e1a8317dab2c7955e56fb7cef2419bcad.png

 

2.  Locks – select Deadlock Graph, Lock:Deadlock and LockDeadlock Chain (all columns for each)

clipboard_e042247e88c7eac7c46c98981639f1ea9.png

 

3.  Stored ProceduresRPC Starting and Completed events (all columns).

clipboard_ee7d3e76e5715357acad06f0794c56654.png

 

4.  TSQLSQL:BatchStarting and SQL:BatchCompleted events ( all columns).

clipboard_e969209c5ca014db7b183276f254e6f45.png

 

Filters:

1.  ApplicationName is usually enabled by default - this is OK.

clipboard_e194012fdf5810567fb0305d32e852289.png

 

2.  Add the following to filter only from the KC production database (actual DB name referenced here):

clipboard_e849c8fc246f9baf6742c183eca25f178.png

 

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
  • Was this article helpful?