0% found this document useful (0 votes)
2K views

Business Objects vs. QlikView

Business Objects (BO) is capable of handling hundreds or thousands of users at once and has strong metadata management capabilities. QlikView has limitations based on RAM size and lacks metadata management. BO provides different tools that can be used in different ways to meet various user needs, while QlikView provides a single tool, making it less flexible but more intuitive. BO also has additional features like semantic layers, live office connectivity, multi-user development environments and user-based security that QlikView lacks.

Uploaded by

Chaitanya Bhure
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2K views

Business Objects vs. QlikView

Business Objects (BO) is capable of handling hundreds or thousands of users at once and has strong metadata management capabilities. QlikView has limitations based on RAM size and lacks metadata management. BO provides different tools that can be used in different ways to meet various user needs, while QlikView provides a single tool, making it less flexible but more intuitive. BO also has additional features like semantic layers, live office connectivity, multi-user development environments and user-based security that QlikView lacks.

Uploaded by

Chaitanya Bhure
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Sr.

No Features&Functionality & i li

BusinessObjects(BO) b ( )

Limitation/Scalabilityover Hasprovenitselfcapableofhandlinghundredsoreven thousandsofusersatonce 1 Data AdHOCCapability 2 3 MetadataManagement

QlickView(QV) l k ( ) QlikViewisaninmemoryBItoolwithalimitationoftheamount ofdatabasedontheRAMsize;whereasothertoolsarehighly scalable.

ll h " " " l " Allowsuserstogeneratetheirown"reports"or"analytics" (e.g.OLAPviews)withoutIT/analystassistance PoorAdhocAnalysis Hasverystrongmetadatamanagementcapabilities LackofMetaDataManagement Providesanarrayofdifferenttoolsthatcanbeusedin d ff h d ff l differentwaystoachievedifferentgoalsormeet requirementsfromdifferentusertypes,fromspeedysimple Providesasingletoolforallusers,meaninglesstrainingand analysis(Polestar)tocomplexdimensionalanalysis implementationtimeandamoreintuitiveinterface,butcan't (Voyager)todashboardstoreporting. adapttospecificuserneeds Yes No Yes No Yes No Yes No MinimumUsersneednottobecompletelydependenton ITteamforanynewobjectorfieldinsertion.Universe High,UsersneedtocallordependonITteamiftheyneednew solvesthepurposehere objectorfieldinareportorinachart BOprovidesasemanticlayerinbetweenthebackend database&thefrontendreportswhichsimplifiesthe complexityofdatabasebymappingtechnnicalterminology touser'susualbusinessterminology NoSemanticLayer BusinessObjectsalsohasLiveOfficeasapluginwhich enablesuserstoImportWebIreportintoexcelwithout actuallyloggingintoInfoView NoLiveofficeconnectivity

4 5 6 7 8

Tools MobileReporting BOExplorer BIWidgets PixcelPerfectReporting

9 ITdependency

10 SymanticLayer

11 LiveOfficeConnectivity

12 QuAWS Exportdataormetadatato Yes 13 XML

C li dl i b h i Obj ComplicatedlogicscanbeputontotheBusinessObjects Universemakingiteasyforusersjusttoselecttheobjects andcreatingtheirownreports.Thesereportscanbesaved, scheduledorusedinadashboard. QVdoeshaveuniverseconcept No

Multiuserdevelopment 14 environment

Yes,Thisfeatureallowsmultipledevelopersworkona singleprojectandtheutilitysynchronisesthepeicesof projecteachdeveloperisworkingwiththemainproject.

No IfyouwanttomakeachangeintheQlikviewscriptor datasourceandwanttoknowtheimpactofthischangeon reportobjectsbeforehand,youcouldbeinproblemandmay havetocheckeachandeveryreportmanuallyanddocumentit. IfyouwanttoseetheSQLgeneratedbehindaquery,youcan notseethatinQlikview AliasOnly

15 ImpactAnalysis 16 SQLGeneration Resolvingcircularloopsand 17 traps Userbased&RoleBased 18 Security RealTimeAnalysis& 19 Reporting

Possible Possible Context&Alias

GraphicalInterfacetoimplementUserbased&rolebasedseNo Yes No

20 DataModelling

21 HardwareMaintenance

Logical,logicalmodelingrequiresmuchmoretimetosetup andistechnicallycomplex.However,whendoneproperly, itallowsmoreanalysisflexibilityandpowerthan associativedatamodels Associative VeryHighasQlickViewusesinmemoryconcept,loadsallthe data&informationinitsRAMthusleadstomuchbigger VeryLow hardwarecost

You might also like