Comparison :- Business Objects vs QlikView

Features of QlikView :-

1. Self-service
2. In-memory performance
3. A lot of the components that you can place on a dashboard, i.e. filters, sliders etc. are handy.
4. Export to Excel, PDF.
5. Extremely fast data visualization. We can go from a high level view to the most granular detail in seconds.
6. Associative search -- there are no pre-defined drill paths. You can visually explore the data and go anywhere you want. You do not have to drill down.and then back up. It makes the data exploration much easier.
7. Very strong data loading capabilities.
8. QlikView is really a platform that you can extend. You can incorporate it into web pages, integrate it with the R open source engine, build custom extensions, etc.
9. QlikView has a "green, white, grey" color scheme. Green is what I selected, white is what is included in that data set, and grey is what is excluded. It is a powerful visualization tool that can show you what is included as well as what is excluded. For data junkies, it is an excellent tool.
10. Very suitable if users have both development and analytical capacity. Great sharing functionalities among small group of users.
11. Good for inter-connectivity among different data sources and tools such as Postgres DB, Excel, etc. Ability to query database directly is a huge advantage.
12. Dynamic reporting functionality with automated scheduled jobs works well across departments, especially where there are end-users that are not Qlikview developers.
13. Very nice and thoughtful UI. Most business end-users love it because it's intuitive.
14. With "in-memory", everything that gets consumed from a dashboard is loaded in memory so it is incredibly fast. Although Qlik touts its mobile distribution capabilities. Microsoft and BO do have in-memory capabilities now
15. The associative model is patented by QlikView. Basically it starts to understand the associations in your data, e.g. if A=B and B=C, then A=C. It means you can build a Qlikview model very quickly. In traditional data warehousing, you work with users and understand their requirements, refine the data model, start to physicality it, tune it, build ETLs. It's a 3 month at best delivery cycle.
16. It link things up. If it doesn't work, you can change things very quickly. You don’t have to write data definition language.

Some Drawbacks of QlikView:-

1. Where you get into trouble, is if you load very large data sets into QlikView, memory not as abundant. They are releasing a tool called data explorer which allows you to do a hybrid approach – load some in memory and some in database. If data is going into frequently used dashboards it goes into memory. 
2. If infrequent access is required and the data set is very large, it makes sense to leave it in the database.
3. Not good for sharing across a medium-to-large organizations and among mixed user groups, some of whom may not have developer's licence to access apps directly. Even if an app is shared as a web-based version, users have little power to make changes and must always rely on developers on the smallest revisions.
4. As a developer, quite unpredictable and erratic in the way it handles data. For example, Qlikview will always try to connect fields among different tables without being told that they are the same, so its associative model is sometimes is erratic. Qlikview is trying to be helpful here but that's not how it should work.
5. Another development issue with Qlikview is with the chart/object property box. It is not intuitive the way they've grouped the various functionalities in different tabs. This makes simple tasks confusing and frustrating. Things that should be found under "Axes", for example, are found in "Numbers" or "Presentation". It took me a year to learn where things are. I think Qlikview should learn from Excel on this.
6. Can be quite buggy if one tries to do a few things at the same times such as running SQL, reading from external data tables, running incremental loads, and creating variables in load script, not to mention using complex functions and set analyses for the front end. This means it doesn't help with business continuity when people leave their job and an app changes hands.
7. Problem with Qlikview can increase with the datasize grow rapidly. Qlikview has certain limitation to store 2 billion rows of data .but they are overcoming to this problem with putting off the data to hardrive only data required for visual would be in RAM.
8. Performance tuning explain plans don’t exist.
9. Documentation is not so good.
10. the governance and meta data management is not great. 
11. Alternate Hierarchies- No concept of Alternate Hierarchies.
12. Qlikview lack in security features too. basically its not having group and roles kind of security structure that Business Objects strongly support.

so this was the QlikView with its features and drawbacks or can say where QlikView need to be improved.

To know about the Business Objects you can go to Whats New in SAP Business Objects 4.x this can tell you about the what business objects has to offer in its latest version.

The main difference that i see with Qlikview and Business Objects is .Qlikview faster development process,In memory capabilities but its lacks in a proper enterprise reporting solution.

Below is the table that compare Business Objects and QlikView across several points:-

#	Product	Business Objects	Qlik View
A	Product
1	Product	Business Objects	QlikView: World's Fastest Growing BI tool. With 10.3 customers being added every working day.
2	Vendor	SAP	QlikTech
			QlikView is an IN-memory based BI tool which can be deployed in a week's time. It comes at HALF the TCO and delivers TWICE the value compared to any OLAP based BI Solution In QUARTER of the TIME
C	Applications
1	Business intelligence	Yes	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
2	Multi dimensional view
3	Strategic planning	Yes
4	Budgeting	Yes
5	Forecasting	Yes
6	Consolidation	Yes
7	Score carding	Yes
D	Hardware and Licenses
1	Warehousing is (Mandate/ Optional)	Mandate	NOT REQUIRED, One of the major advantage of using QlikView is, it does not require database which saves money and very well skilled human resource. With no data warehouse required QlikView can be implemented in a couple of weeks saving a lot of TIME, MONEY AND RESOURCES.
2	Server Licenses(Named/CPU)	Named	Named
3	User Licenses (Name/Concurrent/Unlimited)	Named	Named
4	Web Users	Unlimited	User lic
5	If preparatory Database specify (Technical and Methodology)	NO	NO: 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) This technology overcomes the efforts and time required to build data warehouse, normalization, schema writing, creation of cubes. And Empowers the customer to be independent of the vendor to create and use analytics
E	Technology
1	Supported database		Any OLEDB, ODBC complains which covers althea database in the world today + FLAT FILE, WEBFILE. TEXT FILE DELIMITED FILE. ALSO WORKS WITH SYBASE
	Microsoft SQL Server	Y	Y
	Oracle	Y	Y
	Pervasive SQL	Y	Y
	IBM DB2	Y	Y
	Informix	Y	Y
	Access	Y	Y
	FoxPro	Y	Y
	Progress	Y	Y
	MySQL	Y	Y
2	Supported networks
	Microsoft	Y	YES
	Linux	Y	Y TO CONNECT TO THE DATABASE
	Unix	Y	Y TO CONNECT TO THE DATABASE
	AIX	Y	Y TO CONNECT TO THE DATABASE
	Novell Netware		Y TO CONNECT TO THE DATABASE
	IBM AS/400 (OS/400)	Y	Y TO CONNECT TO THE DATABASE
3	Development tools used to build application		NO THIRD PARTY DEVELOPMENT TOOL REQUIRED. THE CUSTOMER BECOMES VENDOR INDEPENDENT FOR ANY NEW APPLICATION/ CHANGES REQUIRED
4	Report writer used - which one(s)?	Crystal	NO THIRD PARTY TOOL REQUIRED
5	Data Extract Transform Load (ETL) tools - which one(s)?	All Major ETL Tools (bobj Data Integrator)	NOT REQUIRED: QLIK VIEW HAS ITS OWN ROBUST ETL INTEGRATED AS A QLIKVIEW SUITE. THE ETL IS WIZARD DRIVEN CAN BE LEARNT IN A FEW DAYS AND OPERATED BY CUSTOMER HENCE EMPOWER THEMSLEF TO CREAT OWN APPLICATION AS AND WHEN DEMAND ARISES
6	Cubes supported - which one(s)?	All Major OLAP	IN ADDITION TO ITS OWN DATA REPOSITORY QLIKVIEW SUPPORTS ALL MAJOR OLAP CUBES
7	Existing integration to accounting and ERP systems - which systems?	SAP, PeopleSoft, JDE, SSA Global/BAAN, Portal integration kits	ALL ODBC COMPLAINT DATABASE(all the current database in the market) IRRISPECTIVE OF THEIR FRONT END, SAP USING A SAP CERTIFIED CONNECTOR
8	Existing integration to customer relationship management systems - which systems?	Siebel	BY MEANS OF THE GLOBAL STANDARD ODBC, OLEDB CONNECTIONS (all major crm system)
9	Existing integration to payroll systems - which systems?	All Payroll systems on an ODBC data source.	BY MEANS OF THE WORLD STANDARD ODBC, OLEDB CONNECTIONS( all major payroll system)
10	Existing integration to HRMS systems - which systems?	All Payroll systems on an ODBC data source.	BY MEANS OF THE WORLD STANDARD ODBC, OLEDB CONNECTIONS (all major hr system)
F	Features
1	Analytic functionality	Yes	YES
2	Bubble up exceptions	Yes	This feature is better handled where the exceptions are managed at the lower level and not popped to the upper layer and confuses the user. However all precautions are taken to handle the exceptions efficiently.
3	Drill down	Yes	YES
4	Drill through to source data	Yes	DRILL DOWN TO THE TRANSACTIOANL LEVEL. AS AGAINST TO THE AGREGATED DATA IN CASE OF OLAP BASED APPLICATIONS
5	Ranking	Yes	YES
6	Sorting	Yes	YES
7	Restrict results by date range	Yes	YES
8	Includes dashboard	Yes	YES
9	Time trending (for example, over 12 months)	Yes	YES AS MANY YEARS AS THE DATABASE HOLDS
10	Pareto filtering (automatically groups the categories that amount to less than 20% of a row or column total into "other")	Yes	YES
11	Calculations	Yes	YES
12	Counts	Yes	YES
13	Percentage of total	Yes	YES
14	Allocations	Yes	YES
15	Total and Sub-total	Yes	YES
16	Create OLAP cubes	Yes	NOT REQUIRED
17	Data extraction and transformation tools	Yes	INTEGRATED
18	Incremental extraction	Yes	YES
19	Impact analysis - objects impacted by change	Yes	YES
20	Can schedule process to run overnight	Yes	YES
21	Formatting	Yes	YES
22	By dimension	Yes	YES: N DIMENTION
23	By level	Yes	YES
24	By cell	Yes	YES
25	Zero-row suppression	Yes	ZERO/NULL FIELD SUPPRESSION
26	Conditional formatting by cell, e.g., highlight cells below threshold	Yes	YES
27	Returns text (e.g., if value > 90, returns "excellent")	Yes	YES
28	French version	Yes	UNICODE: CAN BE IMPLEMENTED IN ANY LANGUAGE
29	Screens	Yes	YES
30	Reports	Yes	YES
31	Documentation	Yes	YES
32	Metadata	Yes	YES
33	OLAP functionality	Yes	NOT REQUIRED
34	Skip missing levels - support ragged dimensions	Yes	YES
35	Write back	Yes	NO
36	With audit trail	Yes	YES
37	Includes charting tools	Yes	YES
38	Access multiple cubes at a time	Yes	YES
39	Excel client	Yes	YES
40	Internet Explorer client	Yes	YES
41	Netscape client	Yes	Firefox
42	Geographical representation	Yes	YES
43	Drag and drop	Yes	YES
44	Attach notes to cube	Yes	CUBES NOT REQUIRED SAVES TIME AND MONEY
45	Attach notes to cells	Yes	CELLS NOT REQUIRED SAVES TIME AND MONEY
46	Password security	Yes	YES: UP TO THE FIELD LEVEL( BETTER THAN THE LISTING BELOW)
47	By company	Yes	YES
48	By department or division	Yes	YES
49	By menu	Yes	YES
50	By function (view, add, change, delete)	Yes	YES
51	By dimension	Yes	YES
52	By level	Yes	YES
53	By cell	Yes	YES
54	Respect active directory authentication	Yes	YES: CAN BE INTEGRATED WITH ACTIVE DIRETORY AUTHENTICATION FOR A SINGLE LOG ON PER USER
55	Respect database security	Yes	YES
56	Portal generation that includes HTML reports	Yes	YES
57	Report writer	Yes	NOT REQUIRED: INTEGRATED FEATURE
58	Web-based	Yes	YES
59	Generate cube	Yes	NOT REQUIRED: OVERCOMES CUBE DRAWBACKS
60	Drag and drop	Yes	YES
61	WYSIWYG report design	Yes	YES
62	Technology	Yes	YES (AQL)
63	API-enabled (SDK provided)	Yes	YES
64	Web-based (only need browser at client)	Yes	YES
65	For entire application	Yes	YES
66	Support for .NET web services	Yes	YES
67	Support for Java web services	Yes	YES
68	Transfer data to:	Yes	yes
69	Report writer	Yes	QLIKVIEW IS NOT A REPPORT WRITER HOW EVER IT SUPPORTS GENERTING REPORTS AND THIS FEATURE IS INTEGRATED PART OF QLIKVIEW.
70	Excel	Yes	YES
71	PivotTable	Yes	YES
72	HTML	Yes	YES
73	PDF	Yes	YES
74	PowerPoint	Yes	COPY PASTE (CTRL+C, CTRL+V)
75	XML	Yes	YES
76	Views	Yes	YES
77	Crosstabs	Yes	YES
78	Charts	Yes	YES
79	Both crosstabs and chart at the same time	Yes	YES
80	Work flow	Yes	Open to function with third party tools
81	Alerts can be automatically triggered	Yes	YES IN THE FORM OF POPUPS AND CAN BE USED TO AUTOMATE SENDING OF MAILS, ACTIVATE/RUN OTHER APPLICATIONS
82	Dynamically summarizing data without having to rebuild data?		ANALYSIS AT TRANSACTION LEVEL, WITH DRILL DOWN CAPABILITY FROM THE CONSOLIDATED ANALYSIS
83	Ability to pre-calculate results (aggregate) when they are available, or dynamically generating result from atomic information when necessary		YES
84	Ability to control and design cube aggregations		DOES NOT REQUIRE CUBES WHICH CAN HANDLE 3-10 DIMENTIONS ONLY. QLIKVIEW IS BASED ON AQL THAT CAN HANDLE AS MANY DIMENTIONS AS THE FILEDS AVAILABLE
85	Ability to monitor cube performance and tune the cube aggregations accordingly		DOES NOT REQUIRE CUBES WHICH CAN HANDLE 3-10 DIMENTIONS ONLY. QLIKVIEW IS BASED ON AQL THAT CAN HANDLE AS MANY DIMENTIONS AS THE FILEDS AVAILABLE
86	Can the cube be built using either of ROLAP, MOLAP, HOLAP techniques		DOES NOT REQUIRE CUBES WHICH CAN HANDLE 3-10 DIMENTIONS ONLY. QLIKVIEW IS BASED ON AQL THAT CAN HANDLE AS MANY DIMENTIONS AS THE FILEDS AVAILABLE
87	A hybrid database that stores data in relational form and multidimensional form, as appropriate		QLIKVIEW DOES NOT NEED THIRD PARY DATABASE.
88	Is 'What-if" analysis supported		YES
89	GUI based Data Mining Capabilities		YES
90	Enterprise Platform		YES
	Statistical Analytical Modeling		YES
91	Statistics		YES
92	Data & Text Mining		YES
93	Model Management & Deployment
94	Forecasting		YES
95	Econometrics		YES
96	Quality Improvement
97	Operations Research
98	Data Quality		AQL TAKES BUSINESS INTELEGENCE ONE STEP FURTHER THAN THE TREDITIONAL DATA WAREHOUSE ARCHITECHTURE - OLAP BASED SOLUTIONS
	Initial implementation time		1/10 time than Cognos and BO
	Initial implementation cost		1/6 time to implement than Cognos or BO
	Time to proficiency		Only five day Application development training required. Time to become proficient is in days not in month that is 1/6 than Cognos and BI
	Project Success rate		98 % in Comparison to 38 % in OLAP based BI Software.
	TCO		1/2 than any BI tool
	Value		Twice than Cognos and BO