Have you ever wondered why you have to rebind your DB2 applications even when the changes you made had nothing to do with the SQL? Have you ever had one of these binds change the optimal access paths you reviewed and placed in production? If you have you are not alone. That is why we created Avoid Bind. Now you can add performance stability and improve your development throughput by eliminating unnecessary binds during DB2 application development.

If you know what it is like to have a well coded and heavily tested DB2 application blow up in production because of DB2 timestamp mismatch, you need DBRM Check. High rates of application change, and the pressure to quickly move DB2 applications to production, each serve to increase the likelihood of timestamp errors. Even with rigorous change control and the most conscientious due diligence, package lists and bound plans can often be incorrect or out of date. DBRM Check helps you avoid DB2 application outages caused by timestamp mismatches before they impact your business.

If you have been frustrated watching DB2 pick the wrong access path when you knew exactly how the data should be accessed, you need Express Hints. In most cases, the DB2 optimizer does a tremendous job of choosing the best way to access your data. However, there are times when the optimizer has difficulty or just can not determine the best approach. That is why the Optimization Hints feature was introduced in DB2 Version 6. This facility allows the user to override the default access paths chosen by the DB2 optimizer. As implemented, however, the feature is far from easy to use; it requires the user to manually update the PLAN_TABLE and then rebind the plan or package just to determine whether the intended access path is even valid. Express Hints gives your DB2 professionals the ability to easily direct DB2 to select a desired access path.

Have you ever had an unexpected access path change cost your business money or cause client dissatisfaction? You work hard analyzing and tuning your SQL before you move it into production. However, every time you manually bind or DB2 automatically binds your plans or packages, you run the risk of one of your optimal access paths changing. Now you can look before you leap with Path Check. Most access path changes are corrected only after they impact your business. Path Check allows you to bring performance stability to your DB2 applications by detecting and correcting unwanted access paths before they cause costly performance degradation.

Access Path Version to Version Comparison provides you with a series of contrasts between DB2 V6, V7, V8 and V9. We provide you with some test cases that you can run on each of your subsystems. The test cases provide you with a probable situation and a probable modification. We can then contrast the DB2 Optimizer choice for each test case before and after. The goal is to provide your DBAs with surprising results, as they will see where differences occur between releases and where they do not.

Trials provide our clients and potential clients with the opportunity to try out our products for a specified period of time. This way, you can see for yourself whether our tools will provide the value to you that they've provided to other clients. More often than not, DBAs and System Programmers find our tools so useful they hate to see the trial period come to an end. Contact our sales staff and set up a trial for your