What’s going on in your physical data model? How many people can or will update it to match the reality of what’s going on in your databases? Who actually decides what goes into the database design?  How do you choose your primary keys? How do you implement them? Are your datatypes the right ones for the data?

In this presentation we discuss five physical data modeling mistakes that cost you dearly: performance snags, development delays, bugs, and professional respect.  Includes a slightly irreverent look the state of database design in the data profession as well as a look at how to spot them and avoid them.

Audience members will also be able to contribute their war stories of design fails, WTHs and D'ohs.