Databases are they key component in any product or Enterprise system. As multiple versions of these products and systems have been rolled out over the years, a need has been felt to define a database upgrade methodology to overcome the multiple issues that ISVs (Independent Software Vendors) face with ad-hoc upgrade strategies. This paper attempts to summarize the drawbacks of the conventional upgrade approach; recommend the key components of a database upgrade and define their boundaries, roles and responsibilities. Finally, the paper also presents recommendations for changes to the conventional SDLC (Software Development Life Cycle). Keywords: databases, upgrade, methodology, transformation, product, software development, SDLC, ISV