Lucidchart vs erwin Data Modeler by Quest comparison

"The solution's ability to compare and synchronize data sources with data models is fantastic. We use it for that on a regular basis to make sure that changes haven't been made to the database outside of the modeling process. I can take existing databases and reverse engineer them and understand their structure within 15 minutes. If I didn't have Data Modeler it would take hours. It increases our productivity and helps in understanding our legacy application."

"Another feature of erwin is that it can help you enforce your naming standards. It has little modules that you can set up and, as you're building the data model, it's ensuring that they conform to the naming standards that you've developed."

"The generation of DDL saved us having to write the steps by hand. You still had to go in and make some minor modifications to make it deployable to the database system. However, for the data lineage, it is very valuable for tracing our use of data, especially personal confidential data through different systems."

"I have worked with erwin Data Modeler for quite some time and familiarity is its most valuable feature."

"We had some data integration projects, where we needed to integrate it for about 100 databases. Doing that manually is crazy; we can't do that. With erwin, it was much easier to identify which tables and columns could be used for the integration. That means a lot in terms of time and effort as well as my image to the customer, because they can see that we are providing value in a very short time."

"The solution is excellent in providing a visual representation of a database and can generate DDL for implementing changes. We use DDL for logical purposes to review with business people, ensuring they have the required fields for processing. We also use it as a data dictionary for the physical data model to understand all the purposes of the terms. This helps us map the logical and physical terms with the business definition to understand our data."

"It is a scalable solution...The technical support team is fine."

"The logical model gives developers, as well as the data modelers, an understanding of exactly how each object interacts with the others, whether a one-to-many, many-to-many, many-to-one, etc."

"Ease of use is especially critical because if I am conducting brainstorming sessions with my team, I have to be able to quickly put things on the monitor so that I don't lose their attention and focus. Ease of use is definitely helpful when I do that... The fact that I don't get lost within the software and am able to quickly generate visuals onscreen, so that it doesn't break the momentum, is a huge win."

"The interface is really good and it is very easy to use."

"It is a very effective tool for documenting processes and using it has improved our efficiency significantly."

"Easy to work on."

"The ability for Lucidchart to create database schemas or modify existing data structures is strong. That's what I initially introduced it for in our organization. The script that Lucidchart provides works with other systems like Oracle, SQL Server, and Postgres that I can copy-paste, and get a quick dump of metadata and import into has saved me a ton of steps that I didn't have to manually create these tables. I had a lot of things where I still had to put in the linkages between tables, but I didn't have to type in every field name, every data type, and everything else that came in. That saved me tons of time."

"Using Lucidchart for documenting processes is great. The elements are ready to use and it is quick to do."

"Documenting things such as processes, systems, and new teams has been my primary use case. Lucidchart is really, really valuable for its ability to create a process chart from start to end. The web app makes it easy because everything is similar to other tools like Visio but Lucidchart feels a little bit more intuitive. It has been easy to use the web app. I definitely have learned a lot about how to bring in my own graphics or images in place of some of the shapes and I'm able to create and use the arrows within the processes, so it definitely has been useful for me."

"The interface is easy for a layperson to use and adapt to."

"I love the product. I love the ability to get into the code, make it automated, and make it do what I want. I would like to see them put some kind of governance over the ability to make changes to the mart tables with the API, so that instead of just using the modeler's rights to a table -- it has a separate set of rights for API access. That would give us the ability to put governance around API applications. Right now a person with erwin and Excel/VBA has the ability to make changes to models with the API if they also have rights to make changes to the model from erwin. It's a risk."

"I would like to have more data sources from other, different vendors. In recent years, the vendor has reduced the number of data sources, and I would like to have more data sources for every brand. For example, with Oracle, I would like to have compatibility for many versions, including old ones, not just the most recent."

"I still use Visio for conceptual modeling, and that's mainly because it is easier to change things, and you can relax some of the rules. DM's eventual target is a database, which means you actually have to dot all the Is and cross all the Ts, but in a conceptual model, you don't often know what you're working with. So, that's probably a constraint with erwin. They have made it a lot easier, and they've done a lot, but there is probably still room for improvement in terms of the ease of presentation back to the business. I'm comparing it with something like Visio where you can change colors on a box, change the text color and that sort of stuff, and change the lines. Such things are a whole lot easier in Visio, but once you get a theme organized in erwin, you can apply that theme to all of the objects. So, it becomes easier, but you do have to set up that theme."

"Although Quest Software has made tremendous strides in recent years, they need to evolve more in the big data arena; erwin Data Modeler could use a little more work when it comes to big database designs."

"erwin generally fails to successfully reverse engineer our Oracle Databases into erwin data models. The way that they are engineered on our side, the syntax is correct from an Oracle perspective, but it seems to be very difficult for erwin to interpret. What I end up doing is using Oracle Data Modeler to reverse engineer into the Oracle data model, then forward engineer the DDL into an Oracle syntax, and importing that DDL into erwin in order to successfully bring in most of the information from our physical data models. That is a bit of a challenge."

"I find the UI very clunky and very difficult to use. If I add columns to a table the whole workflow could be so much easier. I get frustrated using it. I've tried other tools. I've tried to get off of erwin a few times. I always come back to it because every tool has its own set of problems, and it seems like if I have to pick my poison, I stay with erwin. But so many things that are clunky with it."

"One of the things I've been talking to the erwin team about through the years is that every data model should have the ability to be multi-language... When I was working at Honda, it became very difficult to work with the Japanese teams using just one model. You can have two models, one in English and one in Japanese, but that means you have to keep the updates back and forth, and that always increases the risk of something not being updated."

"I would like to see the ability to support more NoSQL platforms more quickly. In addition, enhancing the graphics to render more quickly would be beneficial for any user."

"There were some things I wish were a little bit more user-friendly. For instance, when you're putting all the stuff onto a document or PDF, there's a set limit of width and height. It would have been very nice in certain situations to be able to drag people on the far edges and move them back up so that everything fits nicely onto the page."

"The main improvement I would like to see is for them to improve the help section on the flow charts or on the formatting."

"I wish there were a lot more automations. For instance, if I'm using a project management software to list out all my WBS [work breakdown structure] I wish Lucidchart had the functionality where it would take all the numbering and generate a tree diagram. Something like that would help so much, but right now it's still a manual task..."

"They should make it more user-friendly. The only option is either to use the existing template with already existing colors and gradients. If you want to do custom colors and gradients, then it's too complicated to use and should be simplified."

"If you're trying to expand a comments box that is sitting on top of the chart, it automatically defaults to assuming you're trying to connect it to the next step in the process, when all you're trying to do is make the box bigger. It automatically goes to the arrow, but I just want to resize the box. That gets a little cumbersome because it does it every single time. It's not just a bug."

"Sometimes, I have created charts with a lot of layers, which locks down parts of the chart and hides parts of the chart to edit it. If they have a better way to deal with specific layers when it gets complex, then that would be helpful. I would like to see something like an illustrator program, where they have a pallet of these layers that I want and don't want as well as being able to see each layer individually. That is the one thing that could be helpful."

"Wireframing can be improved. For mock-ups and wireframing, only 10% of what is required is there. If they can develop this feature, it would be much better because it will then provide everything. Currently, we can design network diagrams, processes, etc., but we should also be able to do wireframing."

"Perhaps it already exists, but if there were software to install the solution on a Mac, that would be helpful. I see that it's not in the App Store, so that's something that could be improved."

"We've continued to use the product for many years and compared it with others on the market. The pricing is reasonable considering what the solution offers and what we pay. There are cheaper tools, but they may not be as robust and easy to use, so it's worth the money."

"Pricing is very high compared to any other product."

"I wish it wasn't so expensive. I would love to personally buy a copy of my own and have it at home, because the next job that I'm looking at is probably project management and I might not have access to the tool. I would like to keep my ability to use the tool. Therefore, they should probably have a pricing for people like me who want to just use the solution as an independent consultant, trying to get started. $3,000 is a big hit."

"erwin Data Modeler by Quest is an expensive solution."

"The solution is expensive."

"erwin is expensive compared to other solutions. We are paying almost $6,000 per seat a month."

"Likewise, the solution is a little pricey."

"Price-wise, erwin Data Modeler is okay. You can purchase a single license and it is not very expensive."

"The pricing is very competitive. It is more cost-effective than some competing products, such as Visio."

"Pricing comes in at about $100 for a year's subscription, which is very reasonable if this is a tool that you will use more than once."

"One of the reasons we were able to get approval within two hours from our management was that it was cheap enough. We have a 3% or 10% collaboration package, which comes out to be 70 bucks a year. It was very cheap, and we had no issues actually getting the full version. It was very affordable for a business."

"I was using the paid version, but at $12 USD per month, I canceled the plan because it was a little bit too expensive for me."

"We signed up for the month-to-month and it charged us all at once for the whole year. I believe we signed up for the $7.99 one. I think that was the price."

"Lucidchart's pricing model is not excessive, as compared to similar products. It is pretty much in line with everyone else."

"The licensing is pretty cost-effective but I haven't considered it on an enterprise level."

"The pricing and licensing are fine. It has a lot of features that I prefer over some of the other programs, which is good. Being that it is web-based, I feel that it is acceptable that it's on a monthly pay basis. However, I think I pay on an annual basis, which is fine with me."