Prepare to put your DB2 SQL code "through the ringer" to ensure it's ready for prime time.
Written by Michael Sansoterra
Typically, developers love writing new code. And while an application is new and business rules are fresh in the mind, it's generally pleasurable to enhance code as change requests meander in. But after the years roll on, and business requirements are forgotten, and complex code looks unfamiliar, then maintaining the code can get downright ugly. How does one know an obscure business rule wasn't violated when changing code? It's usually not until code has been moved into production that the misery starts after a bug rears its ugly head.