Best Practices: Developing for Performance with Toad

There are two types of change that can impact performance once escalated into the production environment: New Development Tuning Existing Application Code New development consists of new functions and features that are pushed into production while tuning for existing code arises when the development process breaks down or the changes are not well tested. This will cause performance issues to arise in production. Why do we need Database Development Best Practices? The development cycle is carefully planned whereas when issues arise in production, it causes a reactive process to occur. Depending on the severity of the performance issues, future development cycles can be impacted, productivity lost and the bottom line affected. When these issues arise, it is due to problematic code and therefore it is the responsibility of the developers to identify and resolve this poorly performing code. In an age of outsourcing, and multi-skilled developers, whose core focus may not be on database development, there is a pressing need for a process to ensure that code being deployed to production is of the highest quality. Management needs to be certain that the investments that they have made to lower the cost of development are indeed paying off. By implementing development best practices organizations ensure that code being deployed to production is of the best quality. Join Quest expert Gary Jerep as he talks you through the Best Practices methodology to develop, optimize and validate your code to ensure SQL code optimized and ready for production, saving valuable time and increasing productivity.