Embarcadero DB Optimizer simplifies SQL optimization and development for application developers with many features for improving productivity and reducing errors. A rich SQL IDE with statement tuning, data source profiling, code completion, real-time error checking, code formatting and sophisticated object validation tools helps streamline coding tasks. DB Optimizer’s user interface helps improve overall productivity with integrated development, monitoring, and tuning components. DB Optimizer offers native support for IBM® DB2® for LUW, Oracle®, Microsoft® SQL Server and Sybase® as well as JDBC support for other DBMS.
DB Optimizer has four components that when used together can optimize your database performance.
SQL Editor: A developer can write Java in Eclipse that calls to the database with SQL. The SQL that calls to the database can be written in the SQL Editor with type ahead, code assist and quick fixes to show the users syntax and correct mistakes. For more information, see Creating and Editing SQL Files (SQL Editor) on page 65.
Load Tester: The SQL code can be run in the Load Tester to test execution by multiple concurrent users. User load testing is so often done my one single user and then problems don’t appear until production with multiple concurrent users. Concurrent user testing is a breeze in DB Optimizer. For more information, see Using SQL Load Editor/Tester on page 153.
Profiler: You can run the Profiler while the Load Tester is executing to show clearly the impact on the database. The profiler can also be used by QA on load simulation. Finally the Profiler can be run on any production database to clearly show load, bottlenecks, and sources of bottlenecks or resource consumption. For more information, see Using Profiling on page 99.
Tuner: Finally if a problem SQL is found on the system the Tuner will show if it’s correctly optimized by the database or not, and if not it will show the best plan and what hints or optimizer directives can be included in the SQL to force the database to use the optimal plan. For Oracle these hints can even be stored in the database so that there is no need to even change the original SQL text. For more information, see Using Tuning on page 157.