Looker is a BI application with an analytics-oriented application server that sits on top of relational data stores. It includes an end-user interface for exploring data, a reusable development paradigm for data discovery, and an API for supporting data in other systems.
N/A
QlikView
Score 7.9 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
Looker
QlikView
Editions & Modules
No answers on this topic
QlikView
Custom
per user
Offerings
Pricing Offerings
Looker
QlikView
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
Required
Optional
Additional Details
Must contact sales team for pricing.
On an perpetual license basis, based on server plus number of users.
Contact vendor for pricing.
Looker was easier to use, better integration with non-standard datastores, such as Prestodb, and Snowflake, and BigTable. Ease of manageability. Creation of reports faster and easier compared to QlikView. Tableau has better heat maps, however, Looker has better drill down in …
Looker stacks up very well against the other tools we have evaluated and used. All the tools have their own pros and cons. Looker had a better edge in terms of visualizations when we chose to use it. After several updates, other tools began to have newer features. Looker still …
I think working on Looker could be hard, but in performance, it can easily overtake Wave and Zoho Reports. The flexibility of the system and it being super fast makes Looker a standalone from other similar software.
Quick dashboards from Google Sheets - Easier to do the graphs than in Google Sheets - Operational dashboards to be used in the day-to-day work - It is good both for retrospective data and to do a pulse check of the current status - Better for not giant amounts of data and not multiple data sources. - If you need a lot of graphs to be displayed on the same page, it can be a bit glitchy during configuration (then the use works fine).
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.
Filtering - you can filter across different dimensions and metrics to get a more specific "cut" of data
Refreshing - data automatically ingests into Looker which allows reports to be updated and backfilled in real time
Conditional Reporting - you can leverage Looker's reporting features to flag when a given metric or KPI falls below or above a specified threshold. For example, if you had a daily sales benchmark in a SAAS organization, you could use Looker to flag whenever daily sales falls above or below the benchmark
Looker is less graphical or pictorial which makes it less attractive
Consumes a lot of memory when there are multiple rows and columns, impacts performance too
At times when we download huge chunks of raw data from Looker dashbords, the time taken to prepare the file is enormous - The user fails to understand if Looker has frozen or if the data is getting prepared in the background for downloading. In turn, user ends up triggering multiple downloads
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.
We've been very happy with Looker so far, and all teams in the organization are starting to see its value, and use it on a frequent basis. It has quickly become our accessible "source of truth" for all data/metrics.
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.
Looker is relatively easy to use, even as it is set up. The customers for the front-end only have issues with the initial setup for looker ml creations. Other "looks" are relatively easy to set up, depending on the ETL and the data which is coming into Looker on a regular basis.
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.
Never had to work with support for issues. Any questions we had, they would respond promptly and clearly. The one-time setup was easy, by reading documentation. If the feature is not supported, they will add a feature request. In this case, LDAP support was requested over OKTA. They are looking into it.
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.
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.
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.
Looker is an off-the-shelf, free tool for Google business users. Other than the internal cost of time to build, we had no costs to set up what we needed to do. Knowledge sharing internally and using templates greatly reduced this cost, making the overall cost very low.
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
Allowing others to self-serve their own analytics and connect it to Looker simply and easily has helped unblock the central data team so they can instead focus on validated dashboards whilst stakeholders manage their day-to-day analysis themselves. Countless engineering hours have been freed up by not having to manage every user permission for each BI tool; we have a BYOBI approach; Bring Your Own BI
Creation and management of a semantic layer (LookML =Looker Modeling Language ) allows peoples sandboxes and production databases to become clutter free. Minor adjustments, conditional fields, and even some modelling can all be done in LookML which doesn't need oversight or governance from the central data team.
LookML, specifying drilldown fields and their sub-queries, as well as generally creating dynamic parameters with Liquid are all great features, but can have a steep learning curve. it may take some time to understand how to create this middle layer correctly, or even pose a risk of inheriting complex code from another source which can be unmaintainable if it becomes too big. Some level of governance is recommended if Looker is used by a large number of editors.
Generate quick reports for requirements that don't require complex calculations. ROI was fine, but Tableau software was much more intuitive for non-technical users on our team
When putting Qlikview reports side by side with Tableau, we ended up delivering Tableau reports since they were quicker to generate and required no technical expertise
