On October 8, 2011, I presented a session on agile database development at SQL Saturday 92. The goal was to help people understand that agile database development makes your business more successful, if you adopt best practices and handle the different risks.
My presentation materials are below. Please note that the demo scripts are designed to work with the AdventureWorks database. Some of them (the design demos) will work in almost any database. Others (the unit test demos) are schema specific.
This includes several useful integrity checks, such as identifying the following:
This includes several deployment best practices, including:
This includes several examples of how to unit test database objects, including:
The world of software development is accelerating. The time between a project idea and its release date is shrinking. That means developers, business staff, and IT personnel need to do iterative (a.k.a. agile) design and development. Agile development for most types of systems is a known quantity. Agile development for databases is harder, and the best practices are more obscure.
Having done a few hundred database releases in an agile fashion, I'll be presenting best practices, anti practices, tips, tricks, demos, and scripts you can use. Don't miss out!Permalink