Try our new research platform with insights from 80,000+ expert users

Microsoft SQL Server Reporting Services vs QlikView comparison

Sponsored
 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

IBM Cognos
Sponsored
Ranking in Reporting
4th
Average Rating
8.0
Number of Reviews
134
Ranking in other categories
BI (Business Intelligence) Tools (7th)
Microsoft SQL Server Report...
Ranking in Reporting
6th
Average Rating
7.8
Reviews Sentiment
8.0
Number of Reviews
18
Ranking in other categories
No ranking in other categories
QlikView
Ranking in Reporting
5th
Average Rating
8.2
Number of Reviews
161
Ranking in other categories
Embedded BI (4th)
 

Mindshare comparison

As of December 2024, in the Reporting category, the mindshare of IBM Cognos is 4.6%, down from 6.1% compared to the previous year. The mindshare of Microsoft SQL Server Reporting Services is 3.7%, down from 5.0% compared to the previous year. The mindshare of QlikView is 3.3%, up from 3.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Reporting
 

Featured Reviews

Carlos Larrad Salgado - PeerSpot reviewer
Improved the quality of our KPIs, while reducing calls to the IT department
I don't like that when we use Colab packages, we get less functionality. For example, you can make groups of data with Excel or with the data sets from the packages, but when you use the Colab packages directly, you can only group the data when you analyze it with Analysis Studio. I think Cognos needs to improve more on this functionality. The user experience is also very important. Cognos is not very easy to understand sometimes, especially when they change the layout but keep the functionality the same. The help is not very graphic and they have no examples. Cognos has to make a big effort to help with understanding the functionality by improving the documentation. There is a lot of documentation, but the examples are hard to find and they should make their help section easier to understand for non-technical users.
Gnanavel-Chakkarapani - PeerSpot reviewer
Offers useful templates but needs to improve the connectivity offered
In Microsoft SQL Server Reporting Services, not much of the interface part is used. With Microsoft SQL Server Reporting Services, its users face issues with the interface after they use Excel or create Microsoft SSIS Packages. The tool's interface is an area of concern requiring improvement. There needs to be an improvement in the product's connectivity so that the tool can connect easily with other third-party databases. In the dashboard, drag and drop functionality needs to improve, especially when compared to other tools like IBM Cognos Analytics and Qlik Sense. Microsoft SQL Server Reporting Services is useful only for standard reports. In IBM Cognos Analytics, query studio can be used by users to drag the data and simply download the reports, so the user doesn't need to have any technical knowledge like developers. Microsoft SQL Server Reporting Services is to be improved to offer features like query Studio, which is provided in IBM Cognos Analytics.
Arjun Meda - PeerSpot reviewer
Useful for data visualization and business intelligence
Many of the features in Qlik Sense need to be available and reintroduced in QlikView. I believe many of the features have been added to QlikView after the layout containers were introduced. QlikView used to be a way more customizable tool than Qlik Sense is in the present time. Improvements are required in the hide and unhide functionality that falls under the layout container feature that has been used in my company in recent times. Hiding off the apps in the app overview tab based on the access was a really good feature that needs to be introduced back in the product since I see that, at the moment, there are multiple groups on the tool, owing to which multiple changes on the QMC part is required to handle the solution. Only the person with access to the dashboard in QlikView could have a link to the dashboard through QlikView's hub or access points. With Qlik Sense, one can see whatever is available in the stream. If a user wants to control everything in the product, then there is no need to make multiple changes in the QMC at the individual app level. The aforementioned area can be considered to improve Qlik Sense.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The basic platform comes with several meta-modelling tools."
"Comparing IBM Cognos to other applications, once a person is trained on it or they have developed a skill set to operate the application, it is best in its category."
"We use IBM Cognos for enterprise analytics and reporting."
"This solution allows you to input a wide range of file formats."
"One of the strong suits of Cognos is its robust corporate reporting capability."
"Using custom controls, it is possible to extend the application with even more functionality and make the application intuitive and attractive."
"The initial setup is quite straightforward."
"The solution's initial setup process is easy."
"The SQL Server Reporting Services makes it very easy to get the data whenever we need it."
"The initial setup is easy."
"In Microsoft SQL Server Reporting Services, the installation and configuration are easy."
"The solution is known for its robust security features."
"Microsoft SQL Server Reporting Services (SSRS) is reliable for management dashboard and reporting purposes. It is helpful for user reporting and administrative tasks, such as monitoring progress. It is easy to use since it is lightweight and integrates well with the SQL Server database, making reporting straightforward. The visualization capabilities enhance our reporting needs with good pagination and KPI features. It integrates well with data servers and workbooks, allowing us to publish reports on mobile applications and tablets easily. Integrating other tools and platforms in our tech ecosystem is generally straightforward. However, if we need to perform something very specialized, we might have to use third-party tools rather than inbuilt options."
"We can create quality reports in real time."
"We were able to embed the report builder within our internal proprietary systems, improving our reporting capabilities."
"The stability of SSRS has been reliable, with minimal issues encountered during our usage."
"QlikView is one of the strongest tools, I would say. Also, it has a very vast capability to process the data"
"On the positive side, QlikView's scripting is a great asset as it functions as an ETL."
"The initial setup is straightforward."
"This is a very cool application with endless options of creativity and visuals."
"The most useful feature of QlikView for me is the QVD concept."
"It is useful to use a tool like this to have a view of data at a point in time. You can extract and create little data sets that you can store, and then over time, you can have a view for tracking changes. Especially when you work with a relational database or a database that's a production database, the data is dynamic, but if you use QlikView, you can take a snapshot of different datasets. In your own time, you can then get insights and report, build, analyze, and draw whatever you need from the data, which is quite useful."
"The initial setup is not very complex."
"One of the good thing is that you can integrate different data source technologies. So you can model your environment without having any of our views running."
 

Cons

"One thing that we really want is the ability to have data portrayed on an image. Cognos is not able to do it at the moment, and that's becoming a requirement from the business side: having an image and then plotting your dataset on top of the image as a map."
"I think the GIS pieces maybe not as good as we would like."
"IBM Cognos's error messages seem to be a bit ambiguous. An error will be encountered and a message will be sent out very ambiguous and after investigating the error message it could be any number of issues. There was never a direct answer to the question or a direct answer to the error messages. Sometimes it would be a generic error message for 21 different solutions. It wasn't very specific, which required a lot of digging around and trial and error trying to fix the problem. The messaging in their error messaging is something needing improvement."
"It is a costly product; it is comparatively expensive."
"Compared to Tableau and PowerBI, the IBM interface is easier to use. However, the drag-and-drop functionality isn't as straightforward. Formatting is also more challenging in the cloud than in other applications, like Power BI. Also, if you encounter an issue, it takes more time to resolve it on the formatting side."
"There are some problems with how Cognos handles huge data sets and when connecting with multiple sources and searching the data."
"The charts and graphics are weak."
"I don't like that when we use Colab packages, we get less functionality. For example, you can make groups of data with Excel or with the data sets from the packages, but when you use the Colab packages directly, you can only group the data when you analyze it with Analysis Studio. I think Cognos needs to improve more on this functionality."
"We encounter some barriers while trying to build a report."
"Tableau is more user-friendly because it doesn't need to do any extra programming. It has drag-and-drop functionality."
"Microsoft SQL Server Reporting Services needs to improve performance."
"We have had issues with the refresh interval since we have too many reports scheduled. Microsoft SQL Server Reporting Services is also expensive."
"It is not easy to integrate the product with other tools in the market."
"The complex tuning for report performance is complicated. There is a lack of native support for source code control. We often need to use separate tools like VS Code or other software to manage version control and changes in the database. It would be beneficial if source code management were integrated directly into SSRS, thus eliminating the need to rely on external tools. While CLI-based operations are exemplary, the trend is towards GUI for a better user experience. Integrating both visualization and source code management within SSRS would simplify the process for users."
"Sometimes, we need to make sure that the configuration stays consistent across the reporting instances. They all connect to the same database. So, it shares that same backend, but the reporting services itself can also be configured. On the application level, for reporting level. And it is, based on my own experience, it is a manual effort to make sure that the reporting servers are configured the same across the environment."
"It would be really nice to have better integration between the solution and Power BI."
"Improvements are required in the hide and unhide functionality that falls under the layout container feature that has been used in my company in recent times."
"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."
"QlikView lacks self-service capabilities, which means users depend on the IT team to make changes."
"QlikView's UI could be more user-friendly."
"Sometimes, dealing with complex reports requires more effort, which could be really improved."
"Scalability really depends on the size of your data and QlikView server architecture. For the biggest data sets, it could become an issue at some point."
"The user interface and ease of use takes a bit of a learning curve to pick up."
"The tool is expensive in Turkey."
 

Pricing and Cost Advice

"It is quite pricy. I think Microsoft BI is cheaper. Tableau might also be cheaper, but it also depends on the usage. If you have very many users, Cognos can be a problem. It could be cheaper than Tableau but not for so many users. If you have a few thousand users, Tableau, which is generally quite expensive, can be cheaper than Cognos."
"The solution is affordable."
"There is a standard license required to use this solution. There are some additional tools but I am not sure if they are an extra cost."
"It is pretty expensive."
"There is some additional licensing that we needed to purchase because we were touching data outside of our core data platform. The cost was approximately $25,000 for the additional licenses, which were approximate 45 licenses. For the application itself, updates, and the core platform it was approximately $50,000. Giving a total cost of $75,000 annually for our usage of IBM Cognos."
"The pricing and licensing policies are comparatively cheaper than other products in the market ."
"It is my understanding that the cost is very low. It's not very expensive."
"IBM Cognos price is on the higher side of the spectrum. However, with the features that it brings, such as correlation analysis, it's worth the money. They should look at the pricing more clearly because it's a little on the higher side."
"The product pricing is reasonable in terms of suitable features for business."
"The price is pretty good."
"The solution is expensive."
"The solution is free to use for developers."
"The pricing is high."
"Value-wise, the solution's pricing is good for the price that we pay."
"The tool's licensing costs are expensive."
"The solution is cheaper than its alternatives."
"The pricing is moderate, in the medium price range."
"I rate the product's pricing a three out of ten."
"It's reasonably priced and falls on the more affordable side."
"I rate QlikView's pricing a five out of ten."
"The setup costs for QlikView are fair as are the yearly maintenance fees. The licensing becomes a bit more expensive and requires some planning for onboarding."
"It has an annual license. It is expensive as compared to other competitive tools that do more for less. In South African rands, we pay about 100,000 to 200,000 a year."
"It is expensive for small companies."
"Pricing is a bit too high and I think licenses should be unlimited."
report
Use our free recommendation engine to learn which Reporting solutions are best for your needs.
824,053 professionals have used our research since 2012.
 

Comparison Review

it_user79932 - PeerSpot reviewer
Feb 4, 2015
Comparison of SAP BO, Tableau, QlikView, Cognos, Microsoft, OBIEE and Pentaho
1. SAP BO/BI Enterprise scalability Security Ease of use Semantic layer 2. Tableau Visualization Data discovery Turnaround time 3. IBM Cognos Enterprise scalability Security In-memory feature 4. MS BI - Flexibility 5. Pentaho - Open source but still enterprise grade 6. QlikView Data…
 

Top Industries

By visitors reading reviews
Educational Organization
55%
Financial Services Firm
7%
Computer Software Company
4%
Government
4%
Financial Services Firm
15%
Government
12%
Computer Software Company
10%
Healthcare Company
7%
Financial Services Firm
18%
Computer Software Company
12%
Manufacturing Company
7%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Seeking lightweight open source BI software
It depends on the Data architecture and the complexity of your requirement. Some great tools in the market are Qlik ...
What do you like most about IBM Cognos?
The solution's most valuable feature is its ease of use, which makes it easily compatible with other tools.
What needs improvement with IBM Cognos?
I need improvements, particularly with the Framework Manager, which has an outdated user interface from older version...
What do you like most about Microsoft SQL Server Reporting Services?
I mainly use the solution for the ease of reporting and for executive dashboards.
What is your experience regarding pricing and costs for Microsoft SQL Server Reporting Services?
Microsoft SQL Server Reporting Services should be okay if you're within the budget. We're just using open-source solu...
What needs improvement with Microsoft SQL Server Reporting Services?
QL Server can support the customer language in the long term, so we can use another language to build some components.
What do you like most about QlikView?
If you correctly use the product for your use cases, it provides value for money.
What is your experience regarding pricing and costs for QlikView?
Qlik Sense's licensing metrics are flexible. They provide packages based on needs, like named licenses, developer lic...
What needs improvement with QlikView?
QlikView lacks self-service capabilities, which means users depend on the IT team to make changes. Qlik Sense offers ...
 

Also Known As

Cognos, Cognos Analytics, IBM Cognos Analytics
SQL Server Reporting Services, Microsoft SSRS, SSRS, MS SQL Server Reporting Services
No data available
 

Learn More

 

Overview

 

Sample Customers

More than 23,000 leading organizations across multiple industries use Cognos. Some examples of Cognos customers include BMW Financial Services, Quinte Health Care, Troy Corporation, Michigan State University, and GKN Land System.
CMS Wire, The New York Times
Canon, Gatorade, Amcor, Panasonic, Fila, Cambridge University Hospitals, Global Retail Bank, North Yorkshire Police department, Lanoo Group Publishers, and AonGroep Nederland.
Find out what your peers are saying about Microsoft SQL Server Reporting Services vs. QlikView and other solutions. Updated: December 2024.
824,053 professionals have used our research since 2012.