Collibra Platform vs. ER/Studio Data Architect

Collibra is well suited where you have multiple reporting environments and multiple source systems. Collibra works well in our environment because we can delegate roles and administration to departments or it can be used in a centralized environment. The ability to customize attributes and assets as well and integrate using the rest api is very important to us.

Incentivized

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

Incentivized

• Data Lineage and traceability
• Easy to customize
• Easy tool to use for business users
• Workflow
• Out of the box metrics

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

• Data Quality and Data Profiling
• Mobile interface

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

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

Collibra offers more features [than alternatives] and is easy for business users to use. We did a proof of concept with Collibra using the Cloud service that allowed us to kick the tires and get a comfort level before we made the investment. At the time of our purchase the market was very immature and is continuing to evolve.

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

• ROI is hard to measure because there are so many soft benefits that come from the tool. We do have a variety of metrics that we track using Collibra to better gauge the maturity of data governance.

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