What is our primary use case?
We have a startup focused on analytics around sports and athletes' performance. The data sits in our platform called Hercules, which is exposed through an ODBC connector or API layer. We're currently building a connector to expose that data in a consumable way, inside Power BI (with one connector for Tableau as well).
What is most valuable?
I love the fact that it's got a very intuitive user interface.
I like the fact that you can create aggregations and view measures and metrics on the fly.
I like the visuals themselves as all of our customers are moving away from Excel and this gives them a very unique way to have their data represented in a more visual manner with active slicing and dicing data right there, with the time dimensions and different dimensions.
I also like the automatic refresh mechanism that it can do. You can have the data refresh automatically every 30 minutes, for example.
The initial setup is pretty simple.
The stability has been pretty good.
The solution can scale.
Technical support has been great.
What needs improvement?
Most clients have MacBooks. Therefore, they use Tableau as Power BI Desktop is not available for the MacBook right now.
When you're building, the documentation sucks. It's a painful experience to find out how to do things inside the connector framework.
I don't like the fact that they need to have a premium excuse to manage larger sets of data. On top of that, there are limitations in building a custom connector. If you want to build a custom connector for your customers, the navigation is flawed. For example, when I build a custom connector to talk to Power BI and report, I want some contextual data of the report, and I want to have what we call incremental refresh. However, incremental refresh right now is only supported in a SQL-based backend. It's not supported for API-based connectors. That's something that we really, really want. We only try to work around it.
Basically, I would love to see that incremental refresh with API-based connectors. I'd also want the report-based contextual information available inside the connector.
The licensing is very confusing.
For how long have I used the solution?
I've been using the solution since about 2014. I've used it for many years at this point.
What do I think about the stability of the solution?
We've found the stability to be fine so far. there are no bugs or glitches. It doesn't crash or freeze.
What do I think about the scalability of the solution?
It's easy to scale if you have the premium model. We just started exploring that right now.
The clients we have that use it are medium-sized businesses. These are basically soccer clubs or sports clubs, who are internally using it. however, we want to give it to a larger audience. We haven't gone there yet, though likely we will in the future.
How are customer service and technical support?
Technical support has been awesome. they are helpful and responsive and we are more than satisfied with the level of service we receive from them.
Which solution did I use previously and why did I switch?
I also use Tableau. I've used Power BI to a larger extent than Tableau, however, we have a startup in which we have an audience on BI and we are doing research to see how many of them are on Tableau versus Power BI.
We didn't previously use a different solution. We started with Power BI because that was one of our device partner's tools of choice. However, we are trying to support Tableau and Power BI now.
How was the initial setup?
The setup was pretty straightforward. I mean the setup for the Power BI Desktop. The download is pretty straightforward. Once you get to do more complex things with it, using the gateway and things like that, then it gets a little complex. On top of that, the documentation is difficult. It's there, however, it's difficult to find.
What's my experience with pricing, setup cost, and licensing?
The licensing is a little convoluted, and not easy to take advantage of. You're able to scale it in the premium model. However, they are very different versions. There's a difficulty in understanding which one of them applies to you and what the costs would be eventually, and what the performance and thresholds are for each one. The documentation might be there, however, for a small company, in order to find out all the aspects of licensing it's not that easy.
Which other solutions did I evaluate?
We've also evaluated Tableau and we use both right now.
What other advice do I have?
We are in the startup program for Microsoft.
I'm on the latest version of the solution. I cannot speak to the exact version number.
It's deployed on the cloud for automatic refreshment service and it's got a gateway on-prem.
It's a very good tool to quickly get started and it does scale, however, as you get into the larger deployments and at a larger scale, it's better to involve a Power BI expert or a partner to help you get there.
I'd rate the solution at an eight out of ten. There's room for improvement from the setup and scale perspective.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner