Replies to This Discussion

Permalink Reply by Andrei on June 21, 2012 at 8:12am

1) NO

2) NOT TRUE: Omniscope has some limited support for cubes, Tableau supports cubes (SSAS), Qlikview does not

3) Tableau 7.x since it can use both RAM and disk as Virtual RAM (can be slow); Qlikview limited by size of RAM. Omniscope has limitations (mostly because of Java) when used with large datasets

4) NOT TRUE; Omniscope can be used as server, if you have correct license (you will get what you pay for)

5) Yes

See more at my blog at http://apandre.wordpress.com/

Andrei

Permalink Reply by jadelim on June 21, 2012 at 8:12pm

Hi Andrei

Thanks for your reply. Can I ask a few more questions regarding Jaspersoft?

1) If compare Jaspersoft to Omniscope and Qlikview, which tools support large data better?

2) Jaspersoft has to pay annually for the license or perpetual?

3) Jaspersoft run on server? The supporting of platform apps is only ipad? Does omniscope have any platform apps like ipad/iphone or andriod?

4) Can jaspersoft support multi-table acess?

5) Is omniscope and jaspersoft both using 64-bit in-RAM DB?

Permalink Reply by Vincent Granville on June 22, 2012 at 5:07pm

What about Python or Perl libraries? Or SAS graph?

Permalink Reply by James Sandoval on June 25, 2012 at 2:47am

Hi - Below is the post I made to LinkedIn last night...

Answers to your Omniscope questions below. Full disclosure, my company is a Visokio value added reseller partner servicing media, marketing and marketing services orgs globally.

* Omniscope does not support multidimensional cubes whereas Tableau and Qlikview does?

Omniscope does indeed support multidimensional cubes.

From Visokio's website: "The OLAP cube data source provides connectivity to MDX-compliant multi-dimensional data secttructures (cubes) such as Microsoft SSAS and other cubes".

More here: http://bit.ly/KvSkvh

* Among the 3 tools, which of the tools is better in supporting large dataset?

Omniscope's scalability and performance are driven to a great extent by the hardware i.e. RAM at play.

Read about Omniscope’s scaling and performance here: http://bit.ly/KvSC54

And here: http://bit.ly/KVI2dR

That said, Omniscope's file-based solution offers up a uniquely powerful opportunity for a "Multi-File Reference Architecture" where 'chains of self-refreshing IOK files can play multiple roles e.g. central management of low weight time slices of data, a central datamart for multi-source data assembly and refresh, central master reports configured and auto-refreshed for specific groups, etc.

And, lastly, while not directly related [it is useful], Omniscope’s reporting data flows can also include ‘by-product’ write-back of output to database tables, enabling the population of new/existing databases/warehouses with scrubbed, transformed data from Omniscope. This is powerful.

* Omniscope does not run from server and have platform apps? The supporting of multi-table access is limited?

Omniscope can indeed run from a server and the support of multi-table access is, if anything, exceptional.

More about Omniscope’s server editions here: http://bit.ly/KVHftm

And a little about Omniscope’s ability to support multiple tables via DataManager: http://bit.ly/zW8nGo

Here’s a doc describing the power & value of Omniscope’s multi-file architecture: http://bit.ly/PWQOX4

I hope this is useful. Reach out to me w/ questions at any time.

Best,
James

@checkyourfuel

Permalink Reply by Thomas J Bate on June 25, 2012 at 12:12pm

Cross link to same discussion running n FlowingData:

http://forums.flowingdata.com/topic/comparison-on-tableau-qlikview-...

 

Omniscope imports from any MDX-compliant cube (principally MS SQL Server SSAS & Oracle Essbase, plus other independents)