ER/Studio vs. Microsoft Visio

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

Incentivized

If I wanted to produce best-in-class deliverables, particularly for an external-facing document where presentation quality matters, I would use Visio. For an organization that wants to standardize and ensure consistent deliverables across teams, I consider Visio a strong option. However, if I need a quick illustration of a process flow or architecture, I would use another tool to avoid spending more time than necessary.

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

• Visio comes with icons that can help differentiate processes within a map. These can be used to be a legend and helps create a visually appealing flow.
• Visio is user-friendly and allows the user to easily navigate through the different creative options that can be used.
• Because this is a Microsoft product, Visio works well with other Microsoft products for easy translation.

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

• For me personally I cannot highlight anything specific that has any bearing on how I use the product. Everything is very straightforward and clearly signposted including template desgins and categories. The layout is easy to navigate and as it's part of the MS Office ecosystem means there is less to learn as I'm used to a lot of the cross product functionality.

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

You need to really understand what you are trying to communicate and deliver with this software package. It allows you to get as simple or as complex (depending on your intended audience) and with the capability of integrating with other Microsoft products like Word, you can deliver a very polished document on a project that would very easily address all aspects from beginning to end.

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

SmartDraw was a program that I used at a prior company before we migrated to Visio. It was not nearly as intuitive to use, and even though it is advertised to be able to offer easy import and export to Visio, when I would export it to a Visio file format and share it with a colleauge, they would always tell me that something would look off with the diagram I sent them. We eventually migrated to Visio at my prior company and thankfully my current company used Visio from day 1.

Incentivized

• 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

• It has allowed us to speed up the creation of flowcharts and organizational charts significantly.
• Microsoft Visio has enabled us to be more effective with our customers by using diagrams to describe our businesses.
• It allows us to organize work with our students more easily.