A customer contacted the Sql Tuning Service to help solve a problem with an important month-end financial report. This report was required to close the accounting period. Over time, the report had gotten slower and was now taking over 3 hours to complete. Frequently modified over time the report SQL was undocumented and 744 lines long. It had been looked at by various groups within the organization, but was considered too time-consuming to tune.

Total Time from start to solution: 2 days   Total Charge: 4 hours

Customer	Sql Tuning Service
The customer submitted the report SQL on the SQL Tuning Service website.
	Tom from the Sql Tuning Service was assigned this case. He examined the SQL and emailed the customer - asking them to run a script to gather some information about the schema.
The client ran the script, it took 40 seconds to run. They returned the script output via email the next morning.
	With this information about the schema, Tom could see that the performance could be improved, reducing the time to 40 minutes. He emailed the customer with a fixed price, for a solution that would complete in 40mins, and explained that in this case, four hours of tuning would be required. The standard Sql Tuning Service guarantee applied - no payment would be required if we did not meet this performance.
The client was happy with the price and guarantee and agreed to have us tune it.
	Tom worked on the SQL statement. With the schema information he was able to simulate the query on our test-rig using the same version of Oracle. He emailed the client his solution. In this case the solution required re-writing of the SQL, no new indexes or other objects were required.
The client tested the new SQL and found that it completed in just under 26 minutes.

This customer contacted the Sql Tuning Service the afternoon following the release of a new application version. They hit a problem they had not seen in testing. A critical problem to the business, they had to resolve it before the next working day or the release would have to be reversed. The problem was caused by a small SQL statement which was running for over three minutes and was delaying the response of a web form. This SQL had taken less than 5 seconds in testing.

Total Time from start to solution: 90 minutes   Total Charge: 1 hour

Customer	Sql Tuning Service
The SQL causing the problem was submitted on the home page of the SQL Tuning Service website.
	Our tuner, Stephen, was assigned this problem. He immediately got in touch with the customer. He asked them to run the schema-info gathering script and some background information
The customer ran the script and returned the information.This script took ten seconds to run.
	The cause of the problem was identified by Stephen - an unusual case that was causing the optimizer to treat the SQL differently. He emailed the customer with an offer to get the SQL running in less than 5 seconds again, for a charge of 1 hour tuning time.
The customer accepted the offer and engaged us to fix the problem.
	Stephen spent the hour analyzing the problem, during which time he had two more questions for the customer. He then emailed them two options, both of them did not make any functional change to the SQL, reducing the testing requirements for the customer. One option was hint for the code, and the other option involved a new index.
The customer took the second option, as they could not change the code easily. The SQL ran in less than 5 seconds on the live system.

This customer had completed the development of new functionality , but could not pass UAT due to performance problems. They were not sure which SQL was causing the problem. They contacted the SQL Tuning Service to see if we could help.

Total Time from start to solution: 3 days   Total Charge: 3 hours

Customer	Sql Tuning Service
The customer contacted the SQL Tuning Service using the 'Tune It' box on the homepage. They described the problems they were having.
	Our tuner, Colin was assigned this case. He emailed the customer and had a conversation to understand the problem. He sent a script to capture and trace the problem process from start-to-end.
The customer ran the script and sent the output back via email.
	Having analyzed the information in the traces, Colin could see one major problem SQL which was responsible for the majority of the problem, and a few other statements that could be improved. He sent back a fixed price and estimates for each of these statements.
The customer choose to have just the major problem statement tuned.
	Colin tuned that statement and sent a solution - the SQL needed to give more information to the optimizer to reduce the amount of data considered.
The development team tested the statement.It reduced the time as expected. Following this success, they choose to get the other three statements tuned.

Top 10 SQLs review
Many of our clients send us a report of the longest running and most resource intensive SQL statements every month for analysis. We identify which SQL queries can be tuned and the potential time and resource savings...

Getting a discoverer report to run quickly for all user parameters
Discoverer allows a user to set a wide range of parameters to filter report results. It can be a challenge to produce report SQL that is consistently fast no matter what user parameters are chosen...

Increasing the output of a data extraction program
A client had a custom data extraction utility written in C++/Pro*C which was in operation for years, but could not now keep up with greater business volumes...

Full analysis of application SQL processing
This software development company needed to get more performance out of the database processing side of its application...

Working live with a Loadrunner testing team
We worked over a weekend with a team performing LoadRunner Performance Tests on a new application. Monitoring SQL processing and fixing problem SQL during the tests...

Do we tune the SQL or the Java code?
The performance problems with a jsp page were clear to see - but what was causing the delay - was it in the SQL or Java code...