Reverse Engineer Databases in Visio 2013

It's in Visual Studio.

al

well, the only thing I found is the SQL Server Diagram tool which is a quite weak tool from my point of view... Or did I miss something?

Thanks,

Thomas

Thomas,

Like you, I was very disappointed in the v2013 support for database and uml.. These two add-ons were carry-overs from when Visio was purchased and were handled by the VS team, which 'deprecated' them. The VS team (afaik) has spent their time on things like the entity suite and trying to compete with Rational Rose. I'd check out the Entity Framework tools.

al

It's in Visual Studio.

al

 

You might start here

http://msdn.microsoft.com/en-us/data/ee712907.aspx

al

I think the question was: has reverse engineering been removed from Visio 2013? Not: is there reverse engineering available in Visual Studio?

Is there any way to get a straight and practical answer in these fora? Business people use them to get pragmatic information on Microsoft products - not to observe petty nerdy one-upmanship.

Does anyone know if the database reverse engineering functionality has been removed from Visio 2013? And, if so, can they please give a straight Yes/No answer? Thanks 

The people who decided to remove it should be fired.

Another example of Microsoft's excessive employee bloat. Each trying to justify his/her existence by doing random (read stupid) things instead of delivering value to loyal customers.

I'm a member of our software standards board and will be recommending the "deprecation" of visio from our list of approved software and seek a replacement. Definitely pulling it out of the current negotiations for their cloud stuff (I think only visio 2013 is offered).

We've already blocked Office 2013 and Windows 8. Now visio. Let's see what else Microsoft releases to drive us further away. Then again, what does Microsoft care. Our company is only about 70K employees strong. A drop in the Microsoft financial bucket.

Angie - that's a little harsh unless that's the sole reason for using Visio.  The problem is that Visio now has too much functionality, and in my experience there was never that much demand for rev eng of dbs.  For me, I would prefer this to be owned by a team (in this case VS) who are going to have the time and resource to add to the functionality, which won't be the case if it stayed with the Visio team.