Interesting Question, I look forward to some other peoples answers, but what I typically do is not use UML for modeling a database. I don't know why but I find UML not a good tool for modeling a database or maybe I find it cumbersome. Now Yes I use UML for modeling my application, and get my ideas for what data needs to be stored there. However then I use Visio For Enterprise Architechs, it has a complete Database Modeling tool in there separated from the UML tools. Which is actually a pretty slick tool in my opinion. I am able to directly push it out from Visio, and set up relations and foreign keys and constraint and rules and stored procedures initial setup I still have to go in and code them. Anyway I find this more usefull for modeling a database than UML. I can then later go back in and see how changes to the database will affect other things.