ER/Studio vs. Microsoft Power BI

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

Incentivized

Microsoft Power BI is great for sales tracking, financial reporting, and real-time operations monitoring. It integrates data from multiple sources, creating interactive dashboards for better decision-making. However, it's less ideal for real-time big data processing, offline access, or when deep customization is needed. It works best for structured reporting but struggles with highly complex data models.

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

• It is great at taking in large amounts of data and housing it all.
• Microsoft Power BI is so user friendly and it's dashboards are very easy on the eye.
• The ease of sharing dashboards makes it great for use across a large company.

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

• It would be easier for users could Microsoft Power BI and Excel used the same programming languages.
• Would like to see the online version of Microsoft Power BI be as powerful as the desktop version.
• Publishing a Microsoft Power BI file online and then having to save the file is somewhat redundant.
• Would like to export each page or chart as an image.

Incentivized

Microsoft Power BI is an excellent and scalable tool. It has a learning curve, but once you get past that, the sky is the limit and you can build from the most simple to the most complex dashboards. I have built everything from simple reports with only a few data points to complex reports with many pages and advanced filtering.

Takes a little bit to get used to it. Not natively intuitive but fairly straight forward to pick up. Also docking it a few points because you can create a really clean, simple UI in Claude very quickly that's faster than building all of this yourself in Microsoft Power BI.

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

It is a fantastic tool, you can do almost everything related with data and reports, it is a perfect substitutive of Power Point and Excel with a high evolution and flexibility, and also it is very friendly and easy to share. I think all companies should have Power BI (or other BI tool) in their software package and if they are in the MS Suite, for sure Power BI should be the one due to all the benefits of the MS ecosystem.

Incentivized

It was integrated with our erp easily and was accessible on cloud.

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

All others apps are enablers and Microsoft Power BI is the visual that end user sees which often adds more value to the end user to make strategic decisions from this. All are equally great but Microsoft Power BI is the end result

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

• We're still early in the adoption process at this company, but we've illustrated how bad data keeps us from being more productive. ~25% of a team's work week was dedicated to effectively cleaning up entries, but it was always seen as a normal to them.

Incentivized