We performed a comparison between QlikView and SQL Server based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Tableau, Oracle and others in Reporting."It excels in supporting database connections and various database types."
"This solution has simplified getting to and understanding our data, no matter where it is housed."
"Easy to analyze data by click-through."
"Data transforming with scripting, and the associative model that lets users browse data in an easy way, are the most valuable features."
"The language support is very good."
"We can scale it if we need to."
"On the positive side, QlikView's scripting is a great asset as it functions as an ETL."
"The initial setup is not very complex."
"Tuning Advisor suggests where to add indexes and from where to remove them. It works like an adviser."
"SQL Server's performance is fine."
"I like that the new version has a memory-optimized table to improve the performance."
"The solution is very common. It's easy to use."
"It's a good option for those that have a lot of Microsoft solutions in use."
"The pricing of the solution is okay. It's less expensive than Oracle, for example."
"I like that it's very easy to use, and Veeam is excellent. There are tons of experts and writers in the area now, and we don't find the same for other databases."
"The most valuable features of SQL Server are the speed, great support, and it is from a known vendor."
"There could be a feature to analyze the sales and accounting data of the client."
"If a user wanted to see something not included in the application the new object had to be created by a power user or developer because Qlik view's scripting has somewhat of a learning curve."
"This solution would be improved with the inclusion of a feature that would allow us to add a common library of (our) commands used in load scripts and expressions, so with a keyword, we would get a drop down to select the command we are looking for, as opposed to the generic help."
"The tool is expensive in Turkey."
"They could provide a user-friendly analysis process rather than specialized IT resource code."
"It is really old. We are moving towards converting everything into a Power BI environment. We want to have a self-service type of BI environment where different levels of users in organizations can log onto a portal and retrieve the data they need or get the necessary insights for decision-making that's important for them or their business unit. They have built a new version of QlikView called QlikSense, which probably competes with newer BI tools, such as Power BI, but they are far behind. That's why we are moving towards a newer tool that's easier to use and has more visualizations to represent the data."
"There is a challenge on the frontend when it comes to browsing data through QlikView, as it isn't entirely compatible with other platforms we use."
"There's room for improvement in the area of management's handling of concerns."
"SQL Server doesn't have proper bitmap indexing, proper columnar databases, or proper implementation of materialized views."
"The pricing in general could be better."
"It needs to be improved to handle big data for large volumes of transactions for big industries. As compared to Oracle Database, SQL Server is not suitable for big data or large organizations where the database size could be more than 100 GB or more. In our country, for a large database and a large volume of transactions, we normally use Oracle Database. Most of the large banks are shifting from SQL Server to Oracle Database because of its slowness."
"We have no vision. We don't know when or how we have been hacked."
"When we are talking about event space architecture, scalability generally comes into play. For example, I might have a hundred thousand transactions a second, and then all of a sudden, I build something that everybody in the world wants. The next thing I know is that I have a million transactions a second. So, to be able to process the throughput, I'd have to scale up, and then when the holidays are over, I'm again down to a hundred thousand transactions, and I want to scale back down. SQL Server is not going to do that. In this way, it is not very scalable. One of the reasons why they want us to use Kafka is so that if we need to, we can do that, but our base program is on SQL Server. So, this is where we would use a Kafka event stack so that if I need more servers, I can just write a command, and I can have more consumers, more brokers, and more producers, and when the holiday season is over, it scales right back down again. SQL Server is not going to do that."
"There are a lot of improvements in the cloud space about which we open a case with Microsoft every now and then. These improvements are not in terms of features or functionality. They are more related to their own compatibility or connectivity on which they keep on working to improve the product."
"The licensing is pretty expensive."
"Its security can be improved. When you look at the Windows environment, it isn't the most secure environment. It is exposed to so many attacks. They continuously need to improve the security of the platform on which it sits."
QlikView is ranked 5th in Reporting with 158 reviews while SQL Server is ranked 1st in Relational Databases Tools with 245 reviews. QlikView is rated 8.2, while SQL Server is rated 8.4. The top reviewer of QlikView writes "Useful for data visualization and business intelligence". On the other hand, the top reviewer of SQL Server writes "A stable, scalable, and easy-to-deploy solution that pretty much covers everything". QlikView is most compared with Tableau, Microsoft Power BI, Amazon QuickSight, TIBCO Spotfire and IBM Cognos, whereas SQL Server is most compared with MariaDB, SAP HANA, Oracle Database, IBM Db2 Database and SAP Adaptive Server Enterprise.
We monitor all Reporting reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.