Microsoft SQL Server Reporting Services vs QlikView comparison

"We get good support from Microsoft."

"In Microsoft SQL Server Reporting Services, the installation and configuration are easy."

"The stability of SSRS has been reliable, with minimal issues encountered during our usage."

"The initial setup is easy."

"It is scalable."

"The SQL Server Reporting Services makes it very easy to get the data whenever we need it."

"We were able to embed the report builder within our internal proprietary systems, improving our reporting capabilities."

"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."

"The most valuable feature of QlikView is the integration with other third-party tools."

"Easy to analyze data by click-through."

"Scripting as per a customer's need, which is a pretty cool feature and not available in other tools."

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

"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."

"QlikView is one of the strongest tools, I would say. Also, it has a very vast capability to process the data"

"It enables us to configure various elements, such as dashboard settings, including factors like color schemes and other customization parameters."

"The product’s most valuable feature is its ability to view the entire data available for analysis."

"It is not easy to integrate the product with other tools in the market."

"The product could be improved by reducing the time it takes to build and deploy reports."

"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."

"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."

"We have had issues with the refresh interval since we have too many reports scheduled. Microsoft SQL Server Reporting Services is also expensive."

"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."

"It doesn't have quite the flexibility of a Tableau or something like that. Many users are more comfortable with Tableau and I'm not quite sure why that is right now, but it seems to be the case."

"Sometimes, dealing with complex reports requires more effort, which could be really improved."

"I would like to see more advanced features from Qlik Sense integrated into QlikView to keep it competitive and up-to-date."

"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."

"They could provide a user-friendly analysis process rather than specialized IT resource code."

"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."

"Installation and deployment could be made easier and quicker."

"The tool is expensive in Turkey."

"There's room for improvement in the area of management's handling of concerns."

"The solution is free to use for developers."

"The price is pretty good."

"The pricing is high."

"The product pricing is reasonable in terms of suitable features for business."

"Value-wise, the solution's pricing is good for the price that we pay."

"The solution is expensive."

"The tool's licensing costs are expensive."

"The solution is cheaper than its alternatives."

"It is quite expensive, rating at around nine out of ten on a cost scale."

"The platform's pricing is considered quite expensive, particularly given the dollar-based pricing."

"The pricing is too high compared to the other solutions on the market."

"Qlik is fairly high in terms of pricing."

"Its licensing costs are moderate, but it can get expensive due to the numerous add-ons available like those for printing."

"QlikView is a reasonably priced solution."

"It is not very expensive. I think it it is on par with other similar products on the market."

"My firm got the product at a cheap price, but in general, I believe that the product is a bit costly."