Oracle Magazine, July/August 2019
Emerging Technologies AUTONOMOUS UPDATE and DELETE statements often enough to negate any perceived performance gains elsewhere Therefore Bettys team doesnt create indexes willy nilly but only after a very careful analysis of the impact on all queries sometimes with the use of Oracle Databases SQL Performance Analyzer feature and even then those indexes are almost always created after the SQL statements have been issued against the database When the SQL statements that use the new indexes cause performance issues DBAs are blamed and DBAs in turn blame the developers for writing the poorly performing queries in the first place Similarly as a result of changing queries indexes created earlier are sometimes no longer needed The DBAs check for usage of indexes and drop them if theyre unused which is also a time consuming not to mention risky exercise for the DBAs Debbie the development manager expects the DBAs to perform this analysis 24 hours a day seven days a week along with everything else they are doing Youve got to be kidding to suggest something that preposterous especially with our lean staff says an enraged Betty Well we certainly cant do it responds Debbie We follow the Agile methodology for development We make small changes perhaps 100 times a week There is no way for us to slow down and check the impact of each change line by line The analysis and changes must come from your team The tension inside the office is so thick you could cut it with a knife Obviously Tanya doesnt like it and wants to end it with a solution acceptable to everyone and also beneficial to Acme She does agree that with Agile development practices and the continuous integration continuous deployment CI CD philosophy its important to maintain the velocity of development So she also understands that these indexing issues must be dealt with after development not before But at the same ORACLE MAGAZINE JULY AUGUST 2019 117
You must have JavaScript enabled to view digital editions.
