We use this solution for dashboards and reporting.
We work in manufacturing and we track any incidents that we have regarding safety.
We use this solution for dashboards and reporting.
We work in manufacturing and we track any incidents that we have regarding safety.
The most valuable feature of this solution is real-time report tracking. For example, we have a report for a human body and the human body is populated with injury data. In real-time, we can see where most of the injuries have occurred.
It is a difficult tool to use and it's hard to figure it out.
It's not user-friendly; more tutorials, training, and better documentation would be helpful.
I have been using Microsoft BI for three months.
We are running the latest version.
I don't have any issues with the stability of Microsoft BI. It's a stable solution.
It's mainly used by developers. We have 10 to 20 developers who are using this solution in our organization.
Technical support could be improved. If you are able to get someone it's great, but if you don't then you are left hanging.
Previously, they were using BusinessObjects.
With the EA agreement, we get access to everything from Microsoft. It just made sense to switch.
The initial setup was completed through our internal Microsoft team.
Licensing costs are on an annual basis. There are no fees in addition to the licensing.
For anyone who is interested in using this solution, they should hire a dedicated Microsoft team to implement it, and get a lot of training.
I don't know it well but I would rate it a five out of ten.
We are using it for reporting, analytics, and data science. We have its latest version.
Microsoft's CRM platform has very limited reporting capabilities. Power BI was able to meet the business requirements for reporting and more in-depth analytics. It is a part of the Microsoft Ecosystem, and there is a straightforward connection from Power BI to CRM.
It is a pretty straightforward and flexible solution for data integration and modeling. It is a low-code solution. When you are doing data integration, you can use the GUI, which is very simple and straightforward. You can also do very intricate custom queries and model it at different levels. It is very easy to use and scalable.
It is kept very current, and there is an update literally every month. However, the interface changes quite randomly with no documentation, which is difficult at the domain and architectural level where you're planning things and engaging the business. Things change frequently, and you wonder where has the button for the new report gone. They should provide better documentation on interface changes.
It should be better optimized. It is supposed to be a data integration tool, but it is doing relatively simple queries. It has its limitations. For example, you can only pull a number of columns. So, there is room for optimization on its ability to integrate multiple data sources.
The desktop tool is very memory-intensive, and again, this is not documented clearly. It requires a heavy CPU and memory use, and it causes your operating systems to become unstable.
I would like to see the ability to create datasets within Power BI. Microsoft is promoting Azure as a cloud solution, but it is dependent upon a desktop component, which seems a little bit deceptive. Data set is the basic element that you report from, but it has to be created on the desktop and then published to the cloud. So, you're in the cloud, and you create a data structure or the data flow, but you can't report from that. You have to leave the cloud, go to your desktop, create the data set on your desktop, and publish it to the cloud. You go back to the cloud and create your report by using that published data set, which is very non-intuitive. If you go to the Microsoft Power BI community, this is a common complaint across the entire community.
I have been using this solution for about 18 months.
It is pretty stable. I haven't determined any major issues.
It is very scalable. It fits perfectly with the larger Azure Data Lake reference architecture. Power BI platform is a fundamental piece, and it becomes scalable to use with other components within that reference architecture.
We're in the process of laying out a three-phase approach. Over the next year, its usage will increase from 50% to 75%. In terms of the number of users, we have around 150 users who are data scientists and data analysts. We have around 5,500 desktop users, and it is a part of 365, which is on every desktop.
There is a lot of online support. We also have Microsoft consultants on contract, and the support comes through them. Their support is very good.
We also have IBM Cognos. We haven't switched. They're being used in tandem. There are different sets of requirements for two different solutions.
I wasn't part of the deployment, but my understanding is that it was pretty straightforward.
We used a Microsoft consultant for implementation. Our experience was good. We don't have any maintenance crew.
I would rate Microsoft BI a nine out of ten.
Microsoft Power BI is an easy tool for data analysis. It's easier to get the data from different data sources and then create a visual representation. Using the tool comes easily and naturally to people proficient with Excel. You need to have an understanding of data modeling and how the data works. Once you work with Power Pivot, I think Power BI will be a better upgrade than other tools in the market.
There are some issues with Microsoft Power BI's integration with OAC because it's currently in the beta phase. We face multiple issues, and the connection drops off multiple times while integrating Microsoft Power BI with OAC and pulling in the data. The solution's integration capabilities have created some issues for us, especially while retrieving data.
I have been using Microsoft Power BI for over seven years.
The solution's technical support has not been very helpful. I have solved my issues by myself and found a workaround for it.
Neutral
I have worked with multiple data visualization tools, such as SAP One and SAP BusinessObjects, where you had different tools for data visualization. I think each tool has its own unique capabilities. The biggest advantage of Microsoft Power BI is its integration with Excel and how it is an upgraded version of Excel. We all know how Excel is used in the market, so Power BI has a strong advantage over its competitors.
I use the solution for myself, and I recommend it to my customers. I would recommend the solution to other users.
The selection of the visualization tool clearly depends on the data sources. I would recommend Microsoft Power BI if I worked for Microsoft. Otherwise, I would recommend other better tools available in the market. It completely depends on the data source and the data volume. I would not recommend Microsoft Power BI if the data volume is very high because it will tend to freeze your report.
Overall, I rate the solution an eight out of ten.
We're using it for sales information and production information. Pushing a report into Power BI makes it easier to use and a little bit more powerful.
We're using the most recent version of the solution.
The flexibility of the program is valuable. We are able to add other information to the reporting information and expand upon it.
We found out that you can't share a report with others unless you have an additional package. That caught us off guard. It came as a program that somebody could go in, build a report, and show it, but you can't share it without having additional licenses.
We've had Microsoft BI for about two years, and we are using it currently. It's a part of Microsoft Teams.
It's stable.
I don't know if it's scalable to the point that we want it. It seems to fit where we have it. We haven't really looked at its scalability. We have other tools, but it works well for what it's doing today.
There are roughly half a dozen users of this solution, and it has sales-related information. There is one driver, and she merges the information. So, there aren't too many rules at this point.
We don't have any plans to increase its usage at this time.
It has been good.
That would've been Excel. So, it isn't a switch; it is growth.
It was easy. We had a good understanding of being able to map two programs together. We had a little training, but otherwise, it was good.
The program installation took a few days, but it took weeks to make the intelligence and the company information look right.
We did it ourselves. We had an individual who worked with it in the past. She picked it up very quickly because she was already trained.
We don't need anybody specific for its maintenance.
We didn't evaluate any other options. The use of Power BI just came with the program, and we installed it. We weren't looking for something different. It just was there for us to use.
My advice to others who are looking into implementing this product is that it is important that they understand their information. They have to understand how the program works, but they also have to understand their information for it to work better.
I would rate it a seven out of 10.
We use Microsoft BI to fetch data from one server in SSMS to another server.
I find many of the features of Microsoft BI valuable, in particular, I use the data flow tasks, look up and incremental loading of data. They have also introduced Hadoop in the control flow task.
I have created particular dashboards for a specific project so that I can show the clients the data related to their needs. Being able to show them a visual of the percentages in a pie chart has been very effective.
The only concern I have faced with Microsoft BI is the time it takes to find out an issue and rectify it.
In my last project, I worked with SSMS as my source and Oracle as my destination. This meant that there were certain compatibility issues between the two. I recommend for incremental load that Microsoft BI can include one task to overcome this concern.
I have been working with Microsoft BI for six years.
Most of my experience was with MS BI, with Power BI the difference is mainly in the report sections. It is more user-friendly compared to SSRS.
If you are not comfortable with SSIS, SSRS, and SSAS, there are many tutorials available for MS BI, especially if you are new to the solution.
I would rate Microsoft BI an 8 out of 10.
Currently, it is used in our financial reporting and financial consideration reports.
It is stable.
It has good functionality and is fully integrated with Microsoft products. If you have already a direct connection or direct integration with Microsoft products, it is very good actually. In some cases, we just developed our BI dashboard and sent it to PowerPoint, for example. It'll be published as the power BI format, which is very good as a feature, to have that capability to just easily populate everything in PowerPoint.
Like all Microsoft products, it is very easy to set up initially.
It's pretty user-friendly.
The product can scale.
Our main concern with Power BI is it doesn't have a connection with the finance application. Power BI is used to present some financial data. However, if there is no direct connection or a ready API to be connected either to Oracle ERP or SAP or a different ERP, it won't be very useful. We need more integration capabilities.
We've been using the solution for five years.
The stability is good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.
The scalability has been great. If a company needs to expand it, it can.
In my organization, there are about 10 to 20 users. The majority have shifted to Qlick.
I haven't contacted technical support in the past. The product has been so stable we haven't needed assistance.
We have multiple BI tools. We previously worked with Oracle BI. Our expectations were not met, and therefore we moved over to Microsoft BI.
In my sector, currently, we are using Qlik Sense. We started using it one year ago.
We are shifting from Microsoft to Qlik due to the fact that we have Oracle ERP as a back end. We are trying to find a technology or BI, which already has a direct connection with this ERP. We went into Qlik Sense for that reason.
The initial setup is straightforward, actually. It is like any other Microsoft product. All of Microsoft's products are straightforward. It isn't complicated. This is one of the main benefits.
I'm not sure how long the deployment process was. I can't speak to how big the technical team was that handled the rollout.
We pay an annual licensing fee.
I would recommend the solution if they already have a Microsoft ERP system. If they have already Microsoft and they have already their financial system in place and if they don't have data movement, Power BI will be very powerful. If a company has different financial systems, they have to track all these data points first, build the business model and then import it to Power BI.
I'd rate the solution at an eight out of ten.
My primary use case of Power BI is to generate dashboards and reports based on past data. Especially for people who aren't engineers, like purely business people, Power BI is helpful because it allows them to analyze and assess their complete business solutions end to end. Power BI provides insights that can help company growth, in terms of revenue and ROI. This solution is cloud-based.
The most valuable feature is that it's easy to use. It's very useful for non-engineers and it is the ultimate solution for providing information and insights. Power BI is the best visualization tool I have ever worked with.
This solution's performance when handling big data could be improved. Right now, if you're handling big data, the application becomes slow and the performance is very low.
Other than that, their licensing costs could be lowered. Microsoft handles everything. For example, if I want to publish a report order from Powerpay, Microsoft doesn't allow me to do this. It's a complete business, but the licensing is very costly. I don't think Microsoft will change their pricing system, though.
I have been using Power BI for the past five years.
Power BI can handle a maximum of one to four gigabytes of data, but the performance becomes very slow if you handle big data. Since this solution is cloud-based, it's always updated to the latest version.
The development is very easy because it depends on each computer. Power BI is a desktop solution that you install on your computer. Once I complete my development, I publish through the internet, which the external users are using. The number of users doesn't matter.
There is a Power BI community, which I'm very happy about. They're there for anything and they're very helpful. In the past, Microsoft has helped us with infrastructure problems.
In the past, I worked with other Python data visualization tools like Dash and Panel. Compared to those tools, Power BI is very easy.
The installation is very straightforward. I did it myself and it took barely ten minutes.
I implemented this solution myself.
You don't need a license for the development, but if you want to publish to external users, you need a license. The licensing is very costly, but I think that since the advantages and benefits of Power BI are so high, people are willing to pay. I can't blame them.
Another visualization tool I've heard of is Splunk, which helps to handle and visualize huge amounts of data. In the future, if Power BI is unable to handle this sort of streaming data, I may consider switching to Splunk. When I extract huge amounts of data with Denodo, Power BI becomes very slow—for example, it takes more time for the display to load. Right now, Power BI can handle a maximum of around one to four gigabytes, whereas Splunk can handle very large amounts of data.
I rate Power BI an eight out of ten. I recommend this solution because it's the best visualization tool I have ever worked with, but the licensing is costly.
We are software developers. We generate data using the basic data connectors that Microsoft provides. We just follow the importing and exporting data around, the Azure platform.
We are doing C# development. We use an SQL server, and we use Power BI. Those are the main three technologies, and then it's just Microsoft to put it together.
We use this solution to create business intelligence reports for the executive users of our applications. We are creating standard business applications like ERP and CRM and e-commerce type applications. Then, we extract a sample of the data, build a simple data warehouse, in the Power BI service, and create some BI reports.
The data visualisation is very attractive from the user's point of view. Users see their reports and think "Wow - that is amazing".
However, it is much harder to prepare data for reporting. I would say 95% of your development time is spent gathering, cleaning, and modelling data. However once that is done reporting is easy.
The capacity needs improvement. It is limited in its capacity in power.
Some of its features are incredibly difficult to understand. There is a learning curve to do the more sophisticated things. For example, paginated reports are complicated. But in general, Power BI, it's not an end-user tool, however much Microsoft pretended it is. We just treat it is like another tool that we use and we deliver the reports to our clients.
The orchestration module for refreshing data flows is something that is missing and we have to do it manually. It should be one of the admin features of Microsoft BI.
I have been working with Microsoft BI for 15 months.
We are using the latest version.
It is a reliable solution.
I haven't tried to scale it, but in theory, I know that is capable. Power BI Premium is easy to scale as long as you have the money.
Inside the business, we only have one user, and outside the business, we have our clients where we have four developers who use this solution.
Our clients are medium-sized companies with 50 to 100 users.
I have not contacted technical support. Google provides the information that we need.
The initial setup is straightforward.
It can take a couple of hours to deploy the gateways, then there is the development of it.
It doesn't require maintenance, but we are forever enhancing the reports. In general, it works without problems.
We are developers, we can complete the installation ourselves.
We view it as an expensive product.
Most of our clients cannot afford the premium capacity.
We just make do with Power BI pro features, which is always a big shame because we know that the premium version has a lot of features that we would like to use, and are not available to us.
There are a few different licensing models.
It ends up being complicated and people don't like paying for things. It's okay if you're working for a large corporation because they can obviously spend thousands of pounds every month on licenses, but our customers cannot.
Licensing is paid on a monthly basis.
Power BI has approximately 20 new features that come out every month. You just have to be patient and eventually, the features come out.
My advice to others would be to do your homework. It's one of those things where you have to get past the marketing. The marketing message is not helpful.
I would suggest that if you are going to use Power BI, you need to use developers who understand what it can do, what it can't do, and how it works.
Then they will then guide you to say, this is the type of report you can expect.
It took me a long time to realize what you can and cannot do with Power BI.
That's why I suggest doing your homework first. It's not as wonderful as Microsoft pretends it to be, but it's not bad, and I am not knocking it, but you have to cut out all the hype that comes with it.
I would rate Microsoft BI a nine out of ten.