Improve performance:
Accelerate new or existing Java applications, even those applications in which the SQL is generated by a framework, such as Hibernate or OpenJPA.
Capture, review, share, and optimize SQL. Facilitate collaboration between developers and DBAs. Replace poor-performing SQL with optimized SQL.
Reduce CPU overhead. In-house testing shows that using pureQuery static execution can significantly increase throughput on existing hardware, ranging from a 60% to a 115% throughput increase. For more details on these results, see the pureQuery Performance Results for DB2 for Linux, UNIX and Windows report.
Enhance security:
Reduce exposure of sensitive data by using the authorization model associated with DB2 static SQL, which grants the EXECUTE privilege on individual packages rather than READ privilege on tables.
Reduce the possibility of malicious SQL injection. Developers or DBAs can now restrict the SQL that will be executed, dynamically or statically.
Improve manageability:
Leverage development metadata to trace an SQL statement to the original application source. Optionally export development metadata to InfoSphere Optim Performance Manager to ease trackback from a deployed application back to the originating source line of code.
Accelerate problem isolation tracing a performance issue to a specific DB2 static package providing better correlation between database workload and the originating application.
Improve version control using DB2 static SQL packages to simplify reverting to previous levels without requiring changes to the application.
Related Software
