Atlan vs. ER/Studio Data Architect

Well suited if you're using a lot of tools that work in tandem with this such as Snowflake, Amazon, S3, Tableau, Power, BI, Redshift, and others. It also has robust functionality for the quality management of metadata sets. The most helpful thing here is all the dashboards that provide visibility in one place. In my experience, less suited for collaboration across teams. Not a ton of ways to do things in real-time together.

Incentivized

Data Architect is well suited at organizations of all sizes. It is never too early or unnecessary to enforce proper modelling and design standards on data solutions, and this tool will help that greatly by providing an industry leading data modelling tool, ability to import ETL mappings for data lineage, enforcing and managing naming conventions through the naming convention tool, and publishing of data dictionaries through the report publisher. I was successfully able to build models, provide traceability, and document source to target with lineage throughout for both the business (by providing business definitions in the descriptions), and technical teams (by documenting ETL instructions in text fields) along with field level mapping (by creating "Attachments" representing data sources, tables, and fields) providing easy search capabilities using business friendly terms

Incentivized

• Here, it is very easy to extract and modify the data.
• We can do very quick and smooth integration over here.
• It's OpenSource framework provides extension capabilities to the API it uses

Incentivized

• ER/Studio has the ability to provide consistent field names and data types through domains, which are templates. This provides a way to have consistent naming of common fields, like CreatedBy and the data types for the fields. They also have the ability to change all the fields that use that domain to a different data type.
• ER/Studio provides the ability to create custom macros. These macros can be used to apply everything from standard fields based on domains to naming all constraints and indexes. I've also used a macro that comes with ER/Studio to spell check field and table names.
• My favorite feature is the ability to compare your data model to databases for deployments of changes, and to other data models.

Incentivized

• API documentation could be improved
• Support team could be quicker in their response
• Not a lot of "help" type information users can self-access

Incentivized

• ER\Studio licensing can be cumbersome and upgrading from one version to another usually takes several phone calls and emails to the licensing group to get the update installed and running.
• The repository can be slow when the model count gets larger. By large I mean 20 to 30 models.
• A nice feature that I would like to see is table comments be displayed on the model along with the attributes. Currently you have to choose between the two.

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

Incentivized

ER/Studio is the most mature, reach in features and quality and therefore useful. Unfortunately, it lacks compatibility with AWS Redshift.

Incentivized

• Atlan has certainly saved time and money by consolidating our metadata sets
• Integrations with Amazon and Tableau have definetely sped up our time to value

Incentivized

• ER/Studio has had a positive impact on my project as we can develop the data model and have a clear understanding of business needs before we continue with the development phase.

Incentivized