You can see from the above screen capture that the Trace Results are divided into 3 sections:

Here is the trace for a query against the Sakila Sample Database: Viewing Trace ResultsĪ trace provides a graphical representation of the execution plan for each query with statistics for its components. You should then see results after the first time period has elapsed. Here's the New Trace dialog with some of the above fields filled in:Ĭlicking on Create Trace that starts tracing according to the provided schedule.

SCHEDULE: scheduling details for executing the trace.

SQL Profiler will terminate the trace when it reaches the row count.

MAX TRACE ROW COUNT: the maximum number of rows for the trace.

QUERY FILTER: search strings or QueryIDs to filter queries for the trace.

Empty means including queries against all databases.

DATABASE FILTER: the databases to trace.

Empty means including queries from all users/roles.

USER FILTER: the users/roles whose queries to include in the trace.

Here are all of the details that you can enter on the New Trace dialog: A prompt may pop up asking you to authorize Navicat Monitor to get relevant data from your instance. On the SQL Profiler page you'll have to select the instance before clicking the + New Trace button:Ĭlicking the Add Trace icon or + New Trace button will bring up the New Trace dialog. The Add Trace icon on the Long Running Queries page You can create new traces on the SQL Profiler, Query Analyzer, and Long Running Queries pages by clicking the Add Trace icon or + New Trace. For example, you can see which queries are affecting performances in the production environment. The data collected from traces may be analyzed and used to troubleshoot performance issues. The SQL Profiler provides graphical query execution details for locating inefficient and slow queries. The Tracing feature is part of the SQL Profiler, which is only available for PostgreSQL. In today's blog we'll learn how to create a trace and view its results. When creating a trace, you can define criteria to filter the data collected by SQL Profiler and set a schedule for executing the trace. Case in point, you can now create traces that collect query data based on selected filters from the server log. Navicat Monitor 3 comes packed with a variety of exciting new features. Trace Queries on your PostgreSQL Instances with Navicat Monitor 3 by Robert Gravelle

Navicat connect to postgresql