Not sure if this is worthy of its own discussion thread but I will start here...

I am looking for some compelling reasons and or real world examples where someone has conquered the question "How do you support using Team Edition For Database Professionals for database development and at the same time the corporate environment insists on managing the schema in a data modeling tool such as ERStudio or Erwin?"

This has become a major bone of contention and I have been unable to spend ample time getting DBPro and external modeling tools to work seamlessly together. My goal is to move the organization closer to Declarative Database Development (as outlined here in this wonderful blog http://blogs.msdn.com/gertd/archive/2009/06/05/declarative-database-development.aspx?CommentPosted=true).

Also just so everyone knows the answer cannot be just simply reverse engineer back into the modeling tool because the push again is to drive the shema (only tables) from the modeling tools.