Lucidchart vs erwin Data Modeler by Quest comparison

"The solution’s code generation ensures accurate engineering of data sources, as there is no development time. Code doesn't even have to be reviewed. We have been using this solution for so long and all the code which has been generated is accurate with the requirements. Once we generate the DDLs out of the erwin tools, the development team does a quick review of the script line by line. They will just be running the script on the database and looking into other requirements, such as the index. So, there is less effort from development side to create tables or build a database."

"Drag-and-drop data modeling and reverse engineering out of databases are the most valuable features of erwin Data Modeler by Quest."

"What has been useful, I have been able to reverse engineer our existing data models to document explicitly referential integrity relationships, primary/foreign keys in the model, and create ERDs that are subject area-based which our clients can use when working with our databases. The reality is that our databases are not explicitly documented in the DDL with primary/foreign key relationships. You can't look at the DDL and explicitly understand the primary/foreign key relationships that exist between our tables, so the referential integrity is not easily understood. erwin has allowed me to explicitly document that and create ERDs. This has made it easier for our clients to consume our databases for their own purposes."

"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."

"It reduces monthly savings by hundreds of thousands of dollars. Think about a company like Costco and all of the points of sale systems in Costco, all of the systems, the applications, but if all the applications in Costco all had their own data model, trying to integrate those, upgrade them and manage their different versions of the same model throughout the store, is an absolute nightmare. It's phenomenally expensive. This helps reduce that cost significantly. I'm talking on the orders of hundreds of thousands of dollars."

"The principal feature that I liked is that the solution has a very graphic interface."

"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'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."

"The best part of Lucidchart is its comfortableness when sharing it with my teammates. Lucidchart provides me a folder for my ERD. I can make a dozen lists of my chart, then share them with my teammates easily through the diagrams of Lucidchart. This is their main comfortableness, which is the reason why I choose Lucidchart rather than some other chart program."

"I really like the drag and drop feature because it makes the work easier. It is very easy to use. All the pieces are very good. All the icons and all the fields are available in the left panel. So, I just click, drag, and then edit a piece. When I showed it to my managing director, he was very inspired, and he also got a premium account for himself."

"The flow chart is most valuable. It is a very user-friendly and simple-to-use product. Quite quickly, I was able to understand how to use it and just get on with my process flow."

"It is important to me that the solution accommodates both Mac and PC users because the developers in our company use Mac, then the business people use Windows. The technical people create the technical architecture using Lucidchart. So, it is important that it is compatible with both the systems."

"One of the features that I really like is the collaboration aspect of it. During the pandemic, it's very important that we're able to collaborate virtually."

"Lucidchart is a lovely tool for creating visual representations of any process or organization."

"There is no alternative to Lucidchart if you want to describe a five-step process with bullet points. I believe every person who ever worked with PowerPoint on any type of documentation and then thought about which tool would actually help to describe what they're trying to do but without the words, would come up with Lucidchart."

"The interface is very good and easy to use. We don't need documentation on how to use it. It is self-explanatory, which is very convenient for a new user."

"It would be nice to have it on the Linux platform, not just Windows. If they can support Linux, there would be a huge market for it."

"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."

"In terms of improvements, support could have been better in terms of installation, especially of workgroups. We struggled quite a bit to get it up and running. Collaboration could have been better from an installation perspective, but it is trivial as compared to what we use it for. Other than that, I don't have much feedback. It works pretty well, and the fact that we've been using it for more than a decade shows that it is quite solid."

"The Bulk Editor needs improvement. If you had something that was a local model to your local machine, you could connect to the API, then it would write directly into the repository. However, when you have something that is on the centralized server, that functionality did not work. Then, you had to export out to a CSV and upload up to the repository. It would have been nice to be able to do the direct API without having that whole download and upload thing. Maybe I didn't figure it out, but I'm pretty sure that didn't work when it was a model that sat on a centralized repository."

"Some Source official systems give us DDLs to work with and they have contents not required to be part of the DDL before we reverse engineer in the erwin DM. Therefore, we manually make changes to those scripts and edit them, then reverse-engineer within the tool. So, it does take some time to edit these DDL scripts generated by the source operational systems. What I would suggest: It would be helpful if there were a place within the erwin tool to import the file and automatically eliminate all the unnecessary lines of code, and just have the clean code built-in to generate the table/data model."

"It does not have a cloud application."

"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."

"The erwin Data Modeler is quite complex to use."

"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."

"I would really like to be able to set default appearance settings for new documents because I have a set of appearance settings that I always use. I end up setting that manually every time. There may be a way to do that, and maybe I am not able to find it. This is my only major point of feedback for improvement. There are other little nitpicky things, such as being able to lock layers without them looking like a big red line around them would be nice, but every graphic design software does that, so I understand why they have that. All my concerns are nitpicks. They're not big."

"One of the major drawbacks is that we have to extract the work in Lucidchart as an image when we want to create a presentation."

"They should continue to bring in more shapes. For example, I saw something cool the other day that was a timeline and in between each step, there was a circle. I thought that that was very clean and that's something that I could see myself using. Lucidchart could come up with more visualizations. I'm not a designer so I would like to have more visuals. That would make my job easier because it would make my job much more professional looking but without having to be a designer myself."

"I'm not a super user, and there might be a way of doing it that I haven't explored, but I was looking for some specific icons that are just standard icons, and I found the icon library to be very focused on architecture icons. It didn't have as many standard or generic icons."

"I don't know if I will be able to add some animations if I want to. I believe the problem may be the program's process flows but if I want to transfer it into a PPP or any other document, I can only do image transfer."

"One of the things that I find frustrating is that all of our Tableau information is on a server, so when I send that out people can't open it and use it. I then have to go back and do extra work to convert everything into an Excel format that everybody can use. It would be really important to me, if I send something out to somebody who doesn't have a Lucid account, that they can just click and see it, instead of having to log in and create an account."

"Although it comes with a lot of pre-existing tools, it would help if it had some more design templates. By now, they must know what kinds of things people are trying out, and that should help them create more templates. I would also like to see a little more automation."

"I don't specifically know what we're paying now. About three years ago, in another organization, I have this memory of 6,000 AUD a seat or something like that, but I am not sure. In the mid-2000s, it was something like 1,200 AUD a seat. I get the impression that there was a price jump when it was spun off from CA as a separate company, which is understandable, but it could sometimes be a barrier in some organizations picking it up. I haven't talked to erwin people yet, but I'm going to suggest to them that they could perhaps think of having an entry-level product that is priced a bit lower, and then, you can buy the extra suite."

"The primary reasons that erwin was selected were that it was much more affordable for us [than Embarcadero] and it was easily maintainable."

"The price should be lower in order to be on the same level as its competitors."

"This company had bought the license for three years, and it's not an individual license. While you can buy a license for each individual, that would be very expensive. There is something called concurrent licenses where you can purchase licenses in bulk and 15 to 20 people can access the license and model. Concurrent licenses are scalable to the number of users and are proportional to the cost."

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

"The tool is expensive."

"An issue right now would be that erwin doesn't have a freely available browser (that I am aware of) for people who are not data modelers or data engineers that a consumer could use to look at the data models and play with it. This would not be to make any changes, but just to visually look at what exists. There are other products out there which do have end user browsers available and allow them to access data models via the data modeling tool."

"Likewise, the solution is a little pricey."

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

"I pay $95 a year for it. It seems like a reasonable price."

"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."

"The pricing and licensing are fine, though I wish they didn't require you to buy the licenses in batches of five."

"There is a nominal charge for the paid version of the product. They have a free version available and from what I could see, there was not much difference between it and the pro version."

"At €167 per user per year, the pricing is slightly higher than Visio, but it's worth it."

"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."

"The price of this product is a little bit high. It is probably 20% higher than what I expected to pay for such a solution."