ER/Studio Data Architect vs. Lucid Visual Collaboration Suite

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

Incentivized

It is hard to think of ways in which Lucid Visual Collaboration Suite would not be best suited to provide an effective tool for any organization to find success in its use. Whether it is a visual display to map an organizational structure, a collaboration to find an answer of how to improve workflow, or even to display the upcoming budget needs, working in Lucid can seamlessly provide that!

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

• Serverless. You don't need to install another program to create diagrams, you just open a new tab and there you are, ready to go.
• Collaboration. You don't need to update your colleague diagram by creating a new file and creating a new file version, you both are in the same diagram and you and all the team are free to update it at any time, at the same time, you are seeing the same thing. That is really helpful and time-saving.
• Shapes. It has any shape that you can think of and Lucidchart is always updating them, I can create an Azure solution architecture, an AWS one, an old on-premise solution. Or just put standard shapes to describe a business process. Providing so many specific shapes help the diagram to express specific information, and for specific teams, that's less text and more visual information, you don't need to put a text below a standard database shape (this is an Azure SQL database), you just put the azure shape and done. That....is beautifully helpful.

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

• Bandwidth - when working with complex workflows spanning multiple shapes and layers, the page tends to slow down and sometimes crash.
• Zooming in & out - when a workflow is spread out over multiple pages, the view can become small even with a large screen.
• Pricing - newly introduced monthly/annual pricing schemes are not as good as previous quarterly payment models.

Incentivized

The interface is easy to use and understand and most features feel very familiar from the start. There are so many features and functions that users may not know it can be done without some instruction. Lucid's champion network is a great, fun resource to learn more about the product.

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

I would rate the overall support for Lucidchart as a 9. The support provided is generally robust and responsive. Their help center, tutorials, and webinars offer extensive resources for users. The ticket-based support system is effective, providing timely resolutions to most issues. Moreover, they actively gather user feedback, demonstrating a commitment to continuous improvement

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

Based on my personal experience, Lucid Visual Collaboration Suite is head and shoulders above any other competitor. Canva is good, but not intuitive at all. Miro is good as well, but not nearly as appealing and still lacks some of the logical functions that LucidSpark has. I’ve also used Apple FreeForm quite a bit, which is a free software with Apple. Once again you can accomplish the same things in any of these software, but Lucid Visual Collaboration Suite is so much better to the point that it is 3-4 times faster to use Lucid than Free Form or Canva.

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

• Though I can't necessarily provide hard numbers, I can confidently say that Lucidchart has saved countless hours for myself and my teams as we don't need to try to develop some type of complex diagram using markup or any kind of code.
• I have previously been able to build a complete ERD using Lucidchart in a past position, which the company never had before. It ended up being used by countless teams in the company and ultimately in a large-scale data stack migration effort.

Incentivized