The document discusses best practices for database deployment management, emphasizing the importance of versioning and automating database changes alongside code changes. It details tools like dbdeploy and liquibase, explaining their functionalities, setups, and the execution of migration scripts. The presentation concludes by advocating the use of documented deployment tools to ensure reliable pre and post-deployment processes.

1. Mike Willbanks Blog: http://blog.digitalstruct.com Twitter : mwillbanks IRC : lubs Talk: http://joind.in/986 Handling Database Deployment ZendCon Unconference 2009

2. What We'll Cover (and not cover) The [Somewhat] Prerequisites

3. Why Use Database Change Management

4. Why To Not Use Database Abstraction Layer Migrations Even You Doctrine! DBDeploy and LiquiBase How It Works (under the hood)

5. Basic Syntax

6. Recommended Structure

7. The [Somewhat] Prerequisites You should be using an issue tracking system.

8. You should be using source code management.

9. You already know how you are deploying your code.

10. Why Database Change Management Do you version your code? Same reasons apply to database deltas (or change sets).

11. Deltas typically are a part of a code change.

12. Ensures the correlation between code revisions.

13. Allows the automation of changes.

14. Ensure you are keeping environments consistent.

15. Allows for reverting back to previous versions (some voodoo magic may be required).

16. The Traditional Way - #fail Developer writes code and applies database change locally.

17. Developer forgets to note change on bug tracking ticket or notify anyone of the change or DBA misses the change, etc.

18. Code deployment and database deployment happens.

19. System is broken... #fail

20. Developer attempts to figure out what happened, “oops factor”.

21. A Better Way Developer writes code and writes a database delta.

22. Developer tests changes locally.

23. Code and Database Delta is committed against a ticket (or at least together).

24. Pre-Deployment Database Changes are Applied.

25. Code Deployment is pushed out.

26. Post-Deployment Database Changes are Applied.

27. System === happiness.

28. Some Process Theory Simplified Database Pre-Deployment Apply database changes compatible with current code, in preparation for new code.