It’s a Team EffortDBA and Developer RolesRead the DocumentationA Guide to the GuidesRoad Maps to ReadingAvoid the Black Box SyndromeDatabase Independence versus Database DependenceDangers of Black Box SyndromeIt’s a Database, Not a Data DumpUse Primary and Foreign KeysTest the Overhead of Referential IntegrityMiddle Tier Checking Is Not a PanaceaBuild a Test EnvironmentTest Against Representative DataDon’t Test with a Single UserDon’t Test in a Dust-Free LabDesign to Perform; Don’t Tune to PerformDon’t Use Generic Data ModelsDesign Your Data Model for EfficiencyDefine Your Performance Goals from the StartWork to Clear, Specific MetricsCollect and Log Metrics over TimeDon’t Do It Because “Everyone Knows You Should”Benchmark, Benchmark, BenchmarkSmall-Time BenchmarkingBig-Time BenchmarkingInstrument the SystemTrace from asktom.oracle.comInstrument for Remote DebuggingUse DBMS_APPLICATION_INFO EverywhereUse DEBUG.F in PL/SQLTurn on SQL_TRACE in Your ApplicationUse Industry-Standard APIsBuild Your Own RoutinesAudit Is Not a Four-Letter WordQuestion AuthorityBeware of Universal “Bests”Suspect Ratios and Other MythsDon’t Look for ShortcutsKeep It SimpleConsider Alternate ApproachesLet the Database Do What It Does BestUse Supplied FunctionalityWe Heard Feature X Is SlowWe Heard Feature X Is ComplicatedWe Don’t Want toWe Didn’t KnowWe Want Database IndependenceSummary