QlikView is a single integrated tool for ETL, DW, Multi-Dimensional Analysis, Dash boarding, Reporting, as per the Butler group user takes couple of hours training instead of weeks taken by traditional OLAP based tools as in the way Business Objects is focusing on Business intelligence, Score carding, Strategic planning, Budgeting, Forecasting, Consolidation etc.
Business objects performance is based on Warehouses, as in QlikView warehouse is not required.
While considering Server/User Licenses both are Named versions.
For Business Objects Web users are unlimitedly configured but in QlikView it’s limited with User license.
QlikView uses its integrated Robust ETL to Extract data from multiple data sources and forms a data repository using its patented Technology (AQL: Associative Query Logic), and Empowers the customer to be independent of the vendor to create and use analytics, But Business Objects required building data warehouse, normalization, schema writing, and creation of cubes.
Both the Reporting tools will shows similarities in Technology wise like Supported database, Supported Networks etc.
QlikView can connect to all major OLAP cubes like Business objects, and they are not using any third party tools used in Business Objects like Crystal Reports.
SAP Business Objects BI solutions reduces BI TCO (Total Cost of Ownership) by providing a single, integrated, scalable, highly available, business intelligence enterprise platform with an award winning service oriented architecture (SOA). Compared to SaaS BI solutions, the cost of QlikView is higher because of the procurement and maintenance of the hardware needed for development, QA and production environments, and costs associated with downtimes. Only when QlikView is compared to on premise BI products does QlikView have a lower TCO.
SAP Business Objects provides a framework of data extraction and analysis that helps business leaders make data centric managerial decisions that will help improve the bottom line and maintain operational stability and efficiency over the long term. QlikView Applications are constrained by how much RAM can be addressed in a single hardware box. As a result, QlikView is designed for gigabytes-scale BI applications. Given a typical 10x compression rate, QlikView performs well on data volumes up to 10-20 gigabytes of compressed data. Since QlikView has to bulk load all data to the system RAM, reloading data is a considerable workload and can take a substantial amount of time. This limits the practical frequency of data updates in case of larger data volumes. QlikView often grows inside of a larger organization via small and isolated departmental deployments. At some point in time, corporate IT will step in and seek to take control. Consolidating and managing separate QlikView deployments is very difficult and requires considerable rework. Lastly, QlikView stores its data in proprietary files. If the need should arise, the proprietary storage format will complicate the migration of data and reports from QlikView to other BI products.
Implementing SAP Business Objects BI solutions better streamlines business intelligence operations by improving the business user information request process.IT department should spend less time intercepting and interpreting information request. Allow users to define information requirements, create queries, analyze and share information with less reliance on IT While QlikView lacks some of the advanced capabilities required for creating highly formatted reports. QlikView is designed for interactive analysis and not for report writing. To create a formatted report in QlikView requires the use of macros and the duplication and maintenance of QlikView objects. Previously created QlikView objects need to be cloned and placed into a “Report Section” in QlikView.
Empower business users by providing them the ability to easily create ad-hoc queries and manage powerful data analysis to obtain deeper business insight regardless of database platform complexity, But QlikView does not offer the richness of MDX and other logical query languages provided by traditional on premise BI products. These languages enable end users to create far more powerful calculations (e.g. via addressing cells position ally in either a materialized or logical cube) than are possible in QlikView. QlikView provides a user interface for users to interactively explore and analyze information based on associations between different data sources. This is a unique approach but because it is not a logical query language, it has limitations.
QlikView implements in a matter of days, as always. Now, QlikView 8 brings real time to in-memory analysis. Using newly released APIs, QlikView can have data streamed into the memory model. Imagine real time stock tickers, and feeds from real-time systems, while the Business Objects requires more time for the implementation.
Business objects require worrying about versioning - both data versioning, and business object versioning, As compared with QlikView.
Creates personalized analysis. Users have the ability to create and save their own personalized QlikViews – without impacting the “master” QlikView. This allows users to define QlikViews according to their individual needs, analyses multiple scenarios and refine results until they get the exact answers needed. In BOs require to write a new object for a new entity - this might not be fully true as design might encourage reuse, but cannot beat the dataset, in which to setup the object have to write zero code.
QlikView Allows people to work better together. QlikView reports, and secure links, can now be sent directly via email and server links. People can share their findings with colleagues, who can then build on that analysis with their own information – continually strengthening the organization’s intelligence like as Business Objects.
In SAP Business Objects Lose any enhancements Microsoft may provide with in future versions of .NET. If in .NET 1.1, shied away from datasets, because of its serialization problems, probably spent a very long time getting business objects working. Only to find out that MS fixed it in .NET 2.0, any way QlikView Does not use.
QlikView’s associative data model is designed for deployment speed and for providing users with an environment that is designed to encourage data exploration. In comparison, the products of leading BI vendors like Oracle, Micro strategy and Business Objects use logical dimensional models that are core to BI best practices that have been proven out over the last 10 years. The reason that QlikView abandons this approach is because traditionally logical modeling requires much more time to set up and is technically complex. However, when done properly, it allows more analysis flexibility and power than associative data models. The Burst approach is to combine the benefits of logical modeling with the quick time to value realized in a SaaS environment.
While QlikView provides a scripting language for integrating and loading data from multiple sources into memory, it does not provide advanced ETL capabilities that are needed for more complicated data integration use cases, like parsing of web log data for sequence analysis and hierarchy tree navigation also In BOs are not directly data bind able. Have to write the code to make that happen.
QlikView makes no distinction between columns that are facts and columns that are attributes. While this is designed to encourage data exploration, it makes the creation of well-defined formatted reports more complicated and time consuming.
The latest release of QlikView provides a feature that allows organizations to run a script for continually updating the in-memory data of a QlikView deployment. Previously, this was not possible but even with this feature, only scenarios where updates to the source system are infrequent and limited in volume would benefit from this. For fully scalable real-time analysis and reporting purposes, a BI platform needs to be able to query the source system or database directly and on demand.
By Comparing with QlikView Concurrency is a bigger pain to manage using BOs. This refers to both thread concurrency and database concurrency Business objects either require writing the equivalent of a data adapter, or they encourage filling the object as the connection is open which severely impacts connection pooling performance. Breaking this single rule can cause application performance to degrade by about 20 times in a concurrent environment.
