Avoid Bind consistently reduces both the CPU and elapsed time required to develop, test, and implement DB2 applications by up to 50%. This is achieved by eliminating major bottlenecks in the development cycle. The ability to quickly move critical applications into production is essential in today's high availability world.

A normal DB2 application development requirement is that all DB2 plans and packages must be bound, even if there have been no SQL changes. This can cause a significant (and unnecessary) increase in the time required for migrations. This delay in the completion of testing and deployment to production is avoidable, since source code changes that do not alter the existing SQL structure of an application do not need to be bound to ensure system integrity.

Avoid Bind allows DB2 application changes to be implemented without unnecessary binds. It allows developers to safely bypass the DB2 bind process while performing selective binds on only the source code that contains altered SQL. The process is transparent to users and requires no dedicated administrator.

Avoid Bind further improves resource efficiency by minimizing exposure to "Access Path Roulette". This phenomenon occurs as a byproduct of the bind process. As part of every bind, DB2 reevaluates, and often changes, the database access paths. Since no one is notified when this occurs, it usually surfaces as an unpleasant surprise when performance degrades suddenly after a migration. Solving the problem after the fact then consumes even more valuable time and resource.

DB2 is both a mission-critical application platform and an enterprise data repository. Development must be free of bottlenecks so that DB2 is available for production tasks. Avoid Bind addresses that need!