Measure the impact of changes on your Oracle environment with Query Performance
A tool to compare the performance of queries in different environments.
Our DBAs know the dedication required to make parameterization changes in a production environment, and the number of manual tests that are required to achieve a minimum of guarantees before tackling a database migration or version upgrade. In addition to the costly software solutions of some manufacturers, in GPS we understood that having a tool that would allow us to compare the performance of queries in different environments, simulating the response before implementing changes, would be at least a TIME SAVER for us and soon for our customers.
Query Performance Advantages
With the information obtained after relaunching the queries, possible errors. Avoiding surprises in production passes.
The behavior of the selected queries, showing their execution plans, times and other performance meters to be compared.
It allows to identify the queries with problems and to make the necessary adjustments that avoid degradations caused by the jumps of version or changes in the database.
Collect data and statistics from the current environment to compare before and after changes. Store this data for later use in new platform changes.
In all of them, the tool offers a detailed report on the impact that the changes would have on the set of chosen queries, thus minimizing risks for the service, and showing all the metrics that will help us make the necessary adjustments that result in a transition without surprises.
What is Query_Performance?
A tool for analysing, comparing and executing queries on Oracle platforms.
GPS Query Performance is a tool that will centralise, based on some native Oracle tools, and by means of a simple software, the whole battery of tests necessary to certify the success of any change, allowing you to compare the performance of queries in different environments.
This tool will help evaluate and measurethe impact of these changes in our Oracle environment, for example:
- Application upgrade, Oracle version or Operating System.
- Code change in the application, due to new regulations or functionality
- Data model modifications: Indexes, partitioning, materialized views
- Hardware changes
- Change of database parameters.
A work is the first element that we must create in order to start working, and on it we will group / organize the rest of the elements of the application: Queries and snapshots mainly. To do this, we must define it by a name and a description.
A snapshot can be created by obtaining the queries from the sources that we have previously discussed (Capture process) and we can also generate it by executing the same queries from the previous snapshot against a different scenario (Replay process).
New in version 1.6. Compare your Oracle queries in PostgreSQL
This new version of Query Performance allows us to compare behaviors and main metrics of the Queries captured in Oracle sources in a PostgreSQL environment.
We will know which Queries run and which do not, as well as what times and consumptions we get in the new PostgreSQL environment to compare it with the current Oracle environment.
What does it compare and how?
We already know what it is, what it does and what it is for, let’s see now how it does it and is organized.
Snapshot: Consists of capturing the performance and statistics of a set of queries.
Work: It will be our “unit or set of tests” in which we will group queries and snapshot as their performances and statistics. A Work is nothing more than a set of queries with their variables and performances (snapshots), or a set of several of these Snapshots.
How does it work and what do you need?
Our tool needs to obtain the queries from the Oracle database, then you can save the queries and their metrics, or launch them again against this or another Oracle environment. With the information obtained after execution, we can generate a detailed report to compare the performance of these queries in different environments..
How do you collect queries and their returns? Well, GPS-QP can obtain the queries and the statistics of its executions from the following sources:
Memory. Queries that run in Oracle are stored in the memory of the database manager. It contains information such as the number of times they have been run, the time it has taken, the readings to disk, etc.
AWR. It is a functionality from the 10g version of Oracle that takes a photo of the state of the manager for a certain time and saves information on the heaviest queries that have been executed in it.
STS (SQL Tuning Set). It is a functionality from Oracle version 11g that allows saving a series of queries to carry out a tuning study on them.
Trace file. It allows us to collect information from an Oracle trace file that we generate from the database. If in addition to the normal trace file we add the information from the tkprof we will have a greater amount of information, such as the users that execute each query for example.
And finally, from other queries that we have stored in our GPS-QP application.
Query Performance is a GPS solution. You can contact us to request information about products or services using the form below.
You can also send an email to the following addresses or call us at +34 918 626 283:
Thank you for your interest.