Microsoft Power BI is a visualization and data discovery tool from Microsoft. It allows users to convert data into visuals and graphics, visually explore and analyze data, collaborate on interactive dashboards and reports, and scale across their organization with built-in governance and security.
$168
per year per user
Red Hat OpenShift
Score 9.2 out of 10
N/A
OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.
$0.08
per hour
QlikView
Score 8.2 out of 10
N/A
QlikView® is Qlik®’s original BI offering designed primarily for shared business intelligence reports and data visualizations. It offers guided exploration and discovery, collaborative analytics for sharing insight, and agile development and deployment.
N/A
Pricing
Microsoft Power BI
Red Hat OpenShift
QlikView
Editions & Modules
Power BI Pro
$14
per month (billed annually) per user
Power BI Premium
$24
per month (billed annually) per user
No answers on this topic
QlikView
Custom
per user
Offerings
Pricing Offerings
Microsoft Power BI
Red Hat OpenShift
QlikView
Free Trial
Yes
Yes
Yes
Free/Freemium Version
Yes
Yes
No
Premium Consulting/Integration Services
No
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Optional
Additional Details
Power BI Desktop is the data exploration and report authoring experience for Power BI, and is available as a free download.
—
On an perpetual license basis, based on server plus number of users.
Contact vendor for pricing.
As mentioned earlier, Power BI is not as mature as QlikView or Tableau and, as a result, is more limited in the kinds of things it's capable of. That said, it's still highly capable of fulfilling most typical BI dashboard requirements. We chose Power BI partly because of a very …
Power BI, Tableau, and QlikView are the market leaders when analyzed on Gartner`s magic quadrant for business intelligence tool. One of the critical drawbacks of all these visionary tools is the absence or expensive back end that are needed to support the infrastructure. …
It has more than 200 plus visuals in-store and is very easy to access. It has a great user community to help each other with an ample amount of responses. Almost all kinds of data sources are available to use and develop the reports Easy to use and learn with a lot of training …
Global Digital Operations Manager - BA Electrification
Chose Microsoft Power BI
Power BI was perfectly integrated in our Microsoft ecosystem what makes everything easier also, the fast evolution that has happened over the last years and their reaction to our needs is something that makes the differents. They listen to the customer and as they do a lot of …
Microsoft Power BI has better pricing, better features in the trial version. Power BI is also integrated with other Microsoft products, so you can publish dashboards to SharePoint pages and to Teams. Power BI is also the easiest to use. It has more wizards and all the pop-ups …
Microsoft Power BI was a little more expensive when comparing it to the competition, but it also offers a lot more options and is more flexible as well. Also, the quality and appearance of the reports and charts was more good looking and aesthetically pleasing than the other …
Power BI does not have the feel of a fully independent and robust BI Solution. It tackles smaller functional or department-level analytic needs and can operate in a small or solo roll-out environment. But scaling up to enterprise would be better suited for Qlik or Tableau. Same …
We selected Microsoft Power BI because it has the best GUI and easy-to-use interface. As part of Microsoft suite, it has the same structure as Office 365 solutions, therefore making it easier to get onboard. At the same time, having backend solutions from Microsoft such as …
Microsoft BI tool does a better job than most of the other software. The reason is excellent visualizations and its capability to connect with various other software and data sources. Tableau does a better job when it comes to tutorials and being more user-friendly. Also …
Power BI takes it to another level with the report and dashboard designing for a wide variety of purposes, and always gives you the option to be collaborative within their native sync features, that is also an advantage to set things up, for example, to promote reports into …
Much easier learning curve and integration with Microsoft Office gives it a leg up. People not knowing they have it, believe it or not, is limiting it's usage. Microsoft really needs to market it!
Power BI is a lot easier to use. The designs are also much nicer. Costs to implement Power BI (minus the existing data infrastructure) is much lower than other tools commercially available. However, the tool is still relatively new and still lacks many common features that …
As mentioned earlier it is free of cost and easy to learn as it is part of the Microsoft suite product. It blends well with ETL package tools such as SSRS and SSIS. It is also easy to distribute the dashboard to users of Office 365. It is a a complete Microsoft product which …
QlikView seems somewhat legacy compared to Microsoft Power BI, with more options to customize and format dashboards with a more enhanced look and feel. QlikView was already widely used in our organization before I came on board and was widely adopted as the single source of …
Each tool has their own pros and cons; QlikView works well for our needs at this time.
Verified User
Executive
Chose QlikView
I think it all comes down to personal preference and integration compatibility with the existing systems in the organization. However, I would argue that Qlik and PowerBI are the top-tier available solutions due to robust features and capabilities, and I would put solutions …
MS Power BI and other BI tools have similar functions to QlikView and some of them also have much cheaper price. However, the strength of QlikView is that it is much easier to use and to learn. If you need to train a new person to learn the tool, it costs around 1-2 days.
QlikView has its own data warehouse, which is the most important reason why would I choose QlikView over any other tools. Apart from that, the feature options are good for the ones who know the tool well but created a steeper learning curve in the beginning. Once you went …
Qlik was less intuitive than Paxata, but less expensive than either microstrategy or PowerBI. Qlik has enough breadth to accommodate most use cases without breaking the bank.
Power BI is cheaper, but more basic. Tableau is more expensive, but with greater capabilities. I feel like the other two are a little more intuitive. My company had Qlikview when I arrived.
Has significantly improved collation of data and visualisation especially with business across Europe. Has given me the ability to see the Site availability at the click of a button to see which Site is in the "money" and seize opportunities based on Market data
Red Hat OpenShift, despite its complexity and overhead, remains the most complete and enterprise-ready Kubernetes platform available. It excels in research projects like ours, where we need robust CI/CD, GPU scheduling, and tight integration with tools like Jupyter, OpenDataHub, and Quiskit. Its security, scalability, and operator ecosystem make it ideal for experimental and production-grade AI workloads. However, for simpler general hosting tasks—such as serving static websites or lightweight backend services—we find traditional VMs, Docker, or LXD more practical and resource-efficient. Red Hat OpenShift shines in complex, container-native workflows, but can be overkill for basic infrastructure needs.
Sales data validations have helped manage our justifications in the past, especially with regard to new product development and new business introduction. It has also been helpful in identifying trends with business impact and direction specific to quarter and monthly sales from ERP data as well as decisions to purchase equipment of staffing based on run rates and product demand.
One thing that can get out of hand is data output - if you aren't careful in your query, you may be overloaded with data dumps and drown in the amount of info you have to filter through. This is a user caution, not a comment on the software itself.
Options for data source connections are immense. Not just which sources, but your options for *how* the data is brought in.
Constant updates (this is both good and bad at times).
User friendliness. I can get the data connections set up and draft some quick visuals, then release to the target audience and let them expand on it how they want to.
We had a few microservices that dealt with notifications and alerts. We used OpenShift to deploy these microservices, which handle and deliver notifications using publish-subscribe models.
We had to expose an API to consumers via MTLS, which was implemented using Server secret integration in OpenShift. We were then able to deploy the APIs on OpenShift with API security.
We integrated Splunk with OpenShift to view the logs of our applications and gain real-time insights into usage, as well as provide high availability.
I wouldn't necessarily say there is look everyday technology transform. I can see a trend wherein Red Hat OpenShift is adopting all the new technology trends and helping their customers align with their priorities and the emerging technology trends. I wouldn't call out various scope for development every day. There is scope for development. It is all how the organizations adopt it and how they deliver it to their customers. I don't want to call out there is scope for development. It's happening. It is a never ending process.
At the moment, I don't have anything to call out. We are experiencing Red Hat OpenShift and we can see every day they're coming up with new features as and when they come up with new features, we want to experience it more and more. We are looking for opportunities wherein this can be leveraged to help our users and partners.
We found that QlikView can be a bit slow in supporting some forms of encryption. It is web-based and we needed to upgrade all of our server to not support the older SSL and TLS 1 protocols, only support TLS 1.2 and TLS 1.3. However, QlikView could not run with TLS 1.2 and TLS 1.3. We had to wait over six months to get a version that would handle the newer TLS versions.
There are so many options with QlikView that you can get lost when developing a visualization. There are still items I have not yet figured out, such as labeling a graph with the name of a selected detail item.
QlikView works by pulling the data it is going to use for visualization into its database. I am a security reviewer and I need to make certain that PII and PHI is not pulled by QlikView for a visualization, otherwise this could become a reportable indecent.
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.
This is the current strategy for the company, most of the products in the organisation are aligning to Openshift and various use cases it support. Also lot of applications are being developed for AI use case, openshift.AI provides opportunity to host and leverage the AI capabilities for these applications
Ease of use, ability to load from pretty much any data source. today I created an application that loaded time sheets from excel that are not in a table format. With Qlik's "enable transformation steps" I was able to automate loads of multiple spreadsheets and multiple tabs easily. Could not do that with any other tool.
Automating reporting has reduced manual data processing by 50-70%, freeing up analysts for higher-value tasks. A finance team that previously spent 20+ hours per week on Excel-based reports now does it in minutes with Microsoft Power BI's automated Real-time dashboards have shortened decision cycles by 30-40%, enabling leadership to react quickly to sales trends, operational bottlenecks, and customer behavior.
As I said before, the obserability is one of the weakest point of OpenShift and that has a lot to do with usability. The Kibana console is not fully integrated with OpenShift console and you have to switch from tab to tab to use it. Same with Prometheus, Jaeger and Grafan, it's a "simple" integration but if you want to do complex queries or dashboards you have to go to the specific console
QlikView is very easy to implement. The installation is very straight forward. QlikView has several different data connectors that can connect to different data sources very smoothly. The user interface to build the reports is very easy to understand. This helps to have a smaller learning curve. Something very helpful is that QlikView is a browser application for the end users. So, you don't need to install any applications on the user's computer.
Redhat openshift is generally reliable and available platform, it ensures high availability for most the situations. in fact the product where we put openshift in a box, we ensure that the availability is also happening at node and network level and also at storage level, so some of the factors that are outside of Openshift realm are also working in HA manner.
Overall, this platform is beneficial. The only downsides we have encountered have been with pods that occasionally hang. This results in resources being dedicated to dead or zombie pods. Over time, these wasted resources occasionally cause us issues, and we have had difficulty monitoring these pods. However, this issue does not overshadow the benefits we get from Openshift.
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.
Their customer support team is good and quick to respond. On a couple of occassions, they have helped us in solving some issues which we were finding a tad difficult to comprehend. On a rare occasion, the response was a bit slow but maybe it was because of the festival season. Overall a good experience on this front.
My experience with the Qlik support team has been somewhat limited, but every interaction I have had with them has been very professional and I received a response quickly. Typically if there is a technical issue, our IT team will follow up. My inquiries are specific to product functionality, and Qlik has been very helpful in clarifying any questions I might have.
I was not involved in the in person training, so i can not answer this question, but the team in my org worked directly with Openshift and able to get the in person training done easily, i did not hear problem or complain in this space, so i hope things happen seamlessly without any issue.
My team attended, but I cannot myself rate, but I think it was good as they've successfully launched a training program at our company themselves for users. It was 3-4 day training.
We went thru the training material on RH webesite, i think its very descriptive and the handson lab sesssions are very useful. It would be good to create more short duration videos covering one single aspect of openshift, this wll keep the interest and also it breaks down the complexity to reasonable chunks.
Training was as expected. The demo environments tend to be more fully featured that our own environment, but the training was clear and well delivered.
"Implementation" can mean a few things... so I'm not sure that this is the answer you want.... but here it goes: To me, implementation means: "Is the user interface intuitive and can I produce meaningful reports with ease?" On that score, I'd say YES. The amount of training required was minimal and the results were powerful. The desktop implementation is a simple, "blank" interface just waiting for your creativity. The pre-populated templates give you a reasonable start to any project -- and a good set of objects to "play around with" if you're just getting started. Finally, note that the "implementation" I used was baked into QuickBooks 2016 Enterprise -- called "Advanced Reporting"..... That integration makes it ultra useful and simple.
Microsoft Power BI is free. If I didn't want to create a custom platform (i.e. my organization insisted on an existing platform that I *had* to use), I'd use Microsoft Power BI. For any start-up or SMB, I'd just use Claude & Grok to build it quickly, also for free. Would not pay for Tableau or Sigma anymore. Not worth it at all.
The Tanzu Platform seemed overly complicated, and the frequent changes to the portfolio as well as the messaging made us uneasy. We also decided it would not be wise to tie our application platform to a specific infrastructure provider, as Tanzu cannot be deployed on anything other than vSphere. SUSE Rancher seemed good overall, but ultimately felt closer to a DIY approach versus the comprehensive package that Red Hat OpenShift provides.
The only other vendor product that I have worked with that provides a similar experience to Qlikview is Tableau. I would recommend Tableau if your use case is to build a fixed dashboard. You can share reports for free without needing to buy additional licenses. I would recommend Qlikview if your users are looking for a more interactive experience. They can create new objects to represent the data which can't be accomplished as easily in Tableau
It's easy to understand what are being billed and what's included in each type of subscription. Same with the support (Std or Premium) you know exactly what to expect when you need to use it. The "core" unit approach on the subscription made really simple to scale and carry the workloads from one site to another.
This is a great platform to deployment container applications designed for multiple use cases. Its reasonably scalable platform, that can host multiple instances of applications, which can seamlessly handle the node and pod failure, if they are configured properly. There should be some scalability best practices guide would be very useful
That is a complicated question and one that's not easy for me to answer. There's a lot of factors that go into all of the stuff that we just don't have an easy way of measuring. And we realize that while we're implementing Red Hat OpenShift, we've tried to start measuring some of that stuff, but we don't have a baseline to go on. So it's hard to say. What I can tell you is general experience with the platform has been extremely positive from the development aspect. Teams have been very, very happy with the speed at which they're able to do stuff. They've been happy with that. The way it works in one environment is exactly the way it works in the next environment because we don't have configuration drift, that type of thing, and has had very positive impacts. But we didn't have a baseline to start with. So I can't talk about getting there faster or anything like that.
You can use the free desktop version to do a lot of reporting and analysis work more quickly so the ROI is huge
QlikView is great at finding outliers such as data entry errors
QlikView is great at helping you quickly discover new insights about your business that can prompt you to take action that can immediately affect your cash flow.
