Microsoft SQL Server Reporting Services vs QlikView comparison

"The initial setup is easy."

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

"I like Microsoft SQL Server Reporting Services' automated reporting feature."

"It is a stable solution."

"With SQL Server Reporting Services, I can create reports and printable reports, known as paginated reports."

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

"We can create quality reports in real time."

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

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

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

"We can scale it if we need to."

"The in-memory feature gives us better insight. It's also easy to drill down into the information and select information."

"The scalability is there."

"It's incredibly fast and can handle large volumes of data without slowing down our operations."

"Associative model - no more cubes."

"You can do a lot of things on the back end which are not possible in the other solutions on the market."

"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 encounter some barriers while trying to build a report."

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

"In this solution, the cost should be reduced for the enterprise edition."

"Tableau is more user-friendly because it doesn't need to do any extra programming. It has drag-and-drop functionality."

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

"They could improve the scalability and stability of SQL Server Reporting Services."

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

"They should offer the capability to directly access data from SaaS environments, as it would simplify the migration process, and while it may seem like a minor enhancement, it would be beneficial to our clients."

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

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

"QlikView lacks self-service capabilities, which means users depend on the IT team to make changes."

"Enhancing user-friendliness would be highly beneficial."

"The user interface and ease of use takes a bit of a learning curve to pick up."

"QlikView's UI could be more user-friendly."

"Improvement in collaboration, between that and publishing of reports and publishing of models."

"The solution is expensive."

"The tool's licensing costs are expensive."

"The solution is cheaper than its alternatives."

"The price is pretty good."

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

"The solution is free to use for developers."

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

"The pricing is high."

"I rate the product's pricing a three 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."

"Qlik is fairly high in terms of pricing."

"It's reasonably priced and falls on the more affordable side."

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

"On a scale of one to ten, where one being low price and ten being high price, I rate pricing a four."

"I rate QlikView's pricing a five out of ten."

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