QlikView Reviews

Ease of use, visualization, intuitive, the Qlik method of ETL, Qlik Sense

Analysis in real time, predictive analytics, reporting

Server performance. Reloading of data sometimes weigh down the server's performance.

1 year

No issues with deployment.

Slight issues with stability.

No issues with scalability.

8/10

8/10

SAP BusinessObjects. Change in business requirements.

Vendor - 7/10.

Yes. SAP BOBJ

The ability to build models that allow business users to do their own what-if analysis on the correct data.

The business was previously using Crystal running on top of hardcoded SQL stored procedures and Qlikview. Qlikview improves development productivity and allows self-help BI.

I would like to see more ‘drag and drop’ functionality as, in my opinion, there is still too much coding required to join tables correctly.

I have been using this solution for 18 months.

As mentioned, we previously used Crystal as well as Oracle OBIEE and both are inflexible and time-consuming.

Initial setup was very straightforward, plus the team had set up Qlikview previously.

We used a vendor team for implementation and that’s probably the way to go first time around, but there must be a skills transfer.

Qlikview are always willing to negotiate pricing, especially if you mention that you are evaluating Tableau as well.

Don’t believe the sales talk that you don’t need a datamart or data warehouse to run Qlikview on top of. It can run against ERP data but then the queries get very complicated and cumbersome.

The ability to customize it. This involves a bit of programming however and that can be an issue. For data visualization, it involves the end-user with self-service BI. It's ETL functions are powerful as well, but this is a bit of an old fashioned approach.

Annual Information from public sector following transparency laws are now publicized in an automated way. Previously, this task used to involve a lot of scripting development and data warehouse routines, such as ETL. Now all this is done using QlikView and raw data.

Actually, Qlik, has decided to move forward with a brand new product, Qlik Sense, so it seems that QlikView can be deprecated as it follows an older approach that pre-dates data visualization in data warehouse and BI.

I've used it for the last two years.

The tool involves too much programming when compared to other tools. It has a development/delivery circle as any internal system development for test/production environment does.

There have been no stability issues and a restart can be automated on a virtual machine.

The product eats all memory you give according to the number of accesses it gets, as the navigation is buffered for future queries. Ideally, the datasets must be summarized to the granularity that the public expects.

9/10

9/10

It was done with technical support, but I wouldn't classify it as complex.

We used a vendor team who were 9/10.

This is not easy to measure, but senior management and the public are satisfied.

It's aligned to the market, but document viewing and sharing constraints are a bit confused and intimidate. They have changed their approach for Qlik Sense.

All proof of concepts used trials and it's not easy to buy a specific product for the government, so the management decision was to apply to an on going acquisition process where the product was already chosen. Two other options were Tableau and Infogram.

Their competitors seem to be more up to date with features and technology. Check whether Qlik Sense is better for you, otherwise you may acquire a legacy tool.

This is a collage of some panels, in Portuguese. The data refers to Brazilian docking ports and loads by type of load, goods, and regions.

Real-time reporting is this product’s most valuable feature to me.

The decision-making process has been streamlined.

The forecasting accuracy should be improved.

I have used QlikView for one year.

I did not encounter any issues with deployment, stability or scalability.

I rate Qlik’s technical support on the high side.

Initial setup was straightforward.

We did it in-house, which I prefer.

It’s about each and every individual and organization.

We were using QlikView for reporting purposes.

The language support is very good. It understands more languages than other products.

The customization features are good.

The performance can be improved.

There is no automation or drag and drop functionality. 

I have not been in contact with technical support.

I have heard of other reporting tools like Tableau but I do not have experience with them.

When you are setting up QlikView, the first thing that you need to do is connect to the database. The length of time it takes depends on the size of the data. We found that for a million records, it will take between two and three minutes.

This is a product that I definitely recommend.

I would rate this solution an eight out of ten.

Data transforming with scripting, and the associative model that lets users browse data in an easy way, are the most valuable features.

Linking different sources of data in a way we could not do before has really helped decision-making regarding our production and focus.

• Error handling

I have been using it 10+ years.

We have not really encountered any deployment issues.

Sometimes when developing QV applications, I encounter almost unexplainable errors that causes QV to crash.

Customer service is very good.

Customer service is excellent.

An in-house team implemented it.

• Better business

To take a good look at needs and the alternatives.

• Integrated ETL
• In-memory data
• QlikView Management Console
• Front-end design.

Implemented some visualizations for:

• Orders Management
• Sales Dashboard
• Contribution Margin Dashboard
• Budget x Real Expenses Management

So now we have better control in some areas, like Sales, Logistics and Financials.

Sales, Marketing, Internal Controls, Factory, HR, Logistics, etc. all still have room for improvement.

Over two years.

No.

Yes, because at the beginning I didn't have the appropriate hardware in our servers. After an upgrade, there were no problems at all.

Upgrading server hardware.

9/10.

8/10.

No previous solution used.

It was complex because we didn't have the correct person (resource) to build the right queries. We then got someone with the right competency and things have been going well.

In-house one.

Not too many developers available in our market (Brazil).

• Instant loading of huge amount of data and immediate display of relationship (both correlation and absence of correlation) between data
• RAD development methodology adoption for QlikView projects
• Set analysis function for simultaneous display of alternative aggregation sets

The backend (scripting) needs improvement to be more like a real ETL BI tool. The script editor is, in my opinion, no more than a basic scripting editor with too-limited debugging features.

I have been using it for five years (still today).

I have not had any issues with deployment, stability or scalability.

Technical support is very good.

The initial setup was straightforward.

We usually implement in-house, but we also rely on external resources.

We are currently using two different BI solutions for our customers: Business Objects and QlikView.

QlikView lets our customers develop data analysis projects independently with a little initial training.

Only a recommendation in order to assure the growth of a project with minimum impact on the previous deployed portion: As much as possible, try to solve data complexity on the backend side (where the logic is easily documentable), rather than in the front-end using only analytic functions.