ER/Studio Data Architect vs. Microsoft Visio

ER/Studio is great for providing data model images for teammates to use when they are not data modelers.

Incentivized

I believe any company or individual that is looking to get a process map visualized; would be a great tool. The tool is a great way to get complex ideas onto “paper” for all to see. Visio can be harder to use if you have an idea that is going in many different directions. If all ideas can fit on one page, this is the tool to use to visualize it all.

Incentivized

• ER/Studio is great for dividing logical and physical design. A logical model can be used with different physical platforms.
• Studio can a useful macro capability that allows me to apply the naming standards across the model with ease and consistency.
• ER/Studio does a very good job at comparing the model with the actual database and generating DDL scripts for production deployments.
• ER/Studio has an excellent reporting and model publishing capabilities allowing me to produce models in the HTML format and publish them for the team as needed.

Incentivized

• The templates for basic flowcharting are simple to use and cover most of the basic functions and touch points in a diagram.
• The variety of included icons and connectors means it's very easy to create floor plans and/or network diagrams.
• The ease at which you can customise connectors with different colours/thickness makes it very effective in overall presentation of a diagram.

Incentivized

• Relationships are a bit on the weaker side. Many times I found orphaned relationships that I could not get rid of, or additional columns that were automatically created during the push to the physical model that appear to be due to key constraint bugs
• There are a lot of bugs introduced when merging keys. I tend to model 2 tables for example logically, establish the relationship, and then merge the additional key column that is automatically created when establishing the relationship. This sometimes causes downstream issues with the physical model (creating duplicate columns with _1 appended)
• Meta-data could be improved. I find it hard to keep descriptions and other meta information clean when copying and pasting from other sources due to formatting tags being introduced on each object (font, size, color, etc.). The attachment feature comes in handy, however I am looking for the ability to cleanly document and map multiple sources to a single target while providing searchability and traceability

Incentivized

• Its inability to delve deeply into micro information successfully.
• It is a paid software which comes after paying a Microsoft licensing fee.
• The cost is high and the integration of the stencil library is unnecessarily fragmented.
• The more you use it, the faster and more effective you will get.

Incentivized

We use Microsoft Visio to keep our diagrams updated and to that end we will need the subscription to keep using the software. Otherwise we will be left with PDF versions of the diagrams.

Incentivized

I think Microsoft Visio is pretty easy to initially pick up and understand the user interface to dive into make basic models. It would be nice if there were some fit for purpose templates so that not as much time needs to be spent on some types of engineering diagram structure. Trying to work on a single Visio file with multiple team members is also a sticking point.

Incentivized

I can call or email support and both get quick turn around. The only issue is they are on the west coast (US) and have a west coast work schedule and I'm on the East coast.

Incentivized

Overall, I feel that Microsoft's support is weak. They are now such a behemoth that their model of putting documentation online for their users to sift through is totally outgrown. Given the amount of money you pay for these licenses, Microsoft should provide easy one-on-one support for their products via email or chat. The idea of paying their rates for support incidents is ridiculous. If you have an enormous amount of time on your hands, use their support websites and you will eventually find a solution most of the time.

Incentivized

ER Studio Data Architect is a global leader in the data modelling space and most other solutions that have support for third party data models include support for ER Studio Data Architect file formats. Many of the features are a bit more intuitive than the competitors and several of our vendors were already using Data Architect themselves which helped solidify the choice.

Incentivized

I have personally never used or evaluated other programs similar to Microsoft Visio. I started using it following an indication from a colleague who told me that our University distributes it free of charge to its users. Since I first used it (more or less three years ago), I have never left Microsoft Visio. Excellent!

• Using ER\Studio to create models and eventually the actual database schema allows for a picture that is understandable to the customer and saves significant time writing DDL to create the database objects (tables, indexes, relationships, constraints...)
• A nice customer interface tool so you can create a web based interface to the metadata for a particular design.
• The tool also supports sub-models so you can break a large project into smaller parts, I find this feature very helpful.

Incentivized

• Greatly enhanced time to create share and finalize documentation.
• Better collaboration between disparate teams, such as marketing opts and sales ops.
• Transparency/visibility into standardize, workflows and processes have led to better team, relationships, and better results that translate directly to the bottom line and ROI.

Incentivized