Objectives:	Show best practices for database change scripting to support development shops Develop methodology to support Extreme / Agile development How to protect large databases from data/scehma corruptions during the change process
Abstract:	We will look at the role of the development DBA and the best practices related to the same. Agile or extreme programming is becoming the buzz word and here we will look at how DBA's and Database Developers can follow some processes to improve and add efficiency to the database changes - both schema and data changes. We will take an approach to club the changes into three logical groups and each group of changes - namely schema changes, data changes and object (procs, functions, triggers) changes, are handled independently. We will show how ot develop the one time framework to support this methodology and track the status of the database changes using this framework. This approach will be useful to salvage large databases when applying a lot of changes to database and prevent prevent refesh of large user schemas. We will show correct order of database changes can be ensured by using this framework that numbers the patches sequentially.
Audiernce Focus:	Developers
Expertise:	Intermediate
Track:	Development
Date:	Thursday, April 17, 2008
Time:	11:00 AM - 12:00 PM