SQL Profiler v14
Inefficient SQL code is one of, if not the leading cause of database performance problems. The challenge for database administrators and developers is locating and then optimizing this code in large, complex systems.
SQL Profiler helps you locate and optimize poorly running SQL code.
Specific features and benefits of SQL Profiler include the following:
- On-demand traces. You can capture SQL traces at any time by manually setting up your parameters and starting the trace.
- Scheduled traces. For inconvenient times, you can also specify your trace parameters and schedule them to run at some later time.
- Save traces. Execute your traces and save them for later review.
- Trace filters. Selectively filter SQL captures by database and by user, or capture every SQL statement sent by all users against all databases.
- Trace output analyzer. A graphical table lets you quickly sort and filter queries by duration or statement, and a graphical or text based
EXPLAINplan lays out your query paths and joins.
- Index Advisor integration. Once you have found your slow queries and optimized them, you can also let the Index Advisor recommend the creation of underlying table indices to further improve performance.
The following describes the installation process.
Step 1: Install SQL Profiler
SQL Profiler is installed by the EDB Postgres Advanced Server installer on Windows or from the
edb-asxx-server-sqlprofiler RPM package on Linux where
xx is the EDB Postgres Advanced Server version number.
Step 2: Add the SQL Profiler library
postgresql.conf parameter file for the instance to include the SQL Profiler library in the
shared_preload_libraries configuration parameter.
For Linux installations, the parameter value should include:
On Windows, the parameter value should include:
Step 3: Create the functions used by SQL Profiler
The SQL Profiler installation program places a SQL script (named
psql command line interface to run the
sql-profiler.sql script in the database specified as the Maintenance Database on the server you wish to profile. If you are using EDB Postgres Advanced Server, the default maintenance database is named
edb. If you are using a PostgreSQL instance, the default maintenance database is named
The following command uses the
psql command line to invoke the
sql-profiler.sql script on a Linux system:
Step 4: Stop and restart the server for the changes to take effect.
After configuring SQL Profiler, it is ready to use with all databases that reside on the server. You can take advantage of SQL Profiler functionality with EDB Postgres Enterprise Manager; for more information about Postgres Enterprise Manager, visit the EDB website at:
If (after performing an upgrade to a newer version of SQL Profiler) you encounter an error that contains the following text:
To correct this error, you must replace the existing query set with a new query set. First, uninstall SQL Profiler by invoking the
uninstall-sql-profiler.sql script, and then reinstall SQL Profiler by invoking the
- On this page