Talk:Essbase

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This paragraph has some problems:

Many Hyperion products were renamed in 2005, giving Essbase an official name of Hyperion® System™ 9 BI+™ Analytic Services™, but the new name was largely ignored by practitioners. The Essbase brand was later returned to the official product name for marketing purposes, but the server software still carries the "Analytic Services" title.

Essbase was called Hyperion® System™ 9 BI+™ Essbase Analytics™. There were other products with Essbase in the title that were renamed with the Analytic Services name (for example Essbase Deployment Services -> Hyperion System 9 Analytic High Availability Services), but Essbase itself has always kept the same System 9 name. You can see more about product names here: http://dev.hyperion.com/products/product_mig_disc.cfm

I'd welcome suggestions on how to update this paragraph.

  • I do remember a period where the Essbase name was pretty hard to find, but I'm happy to be corrected. But they do indeed seem to have put Essbase back in the brand name -- there's no mention of "Analytic Services" as a product at all on the (marketing) web site any more, just "Hyperion® System™ 9 BI+™ Essbase Analytics™" and "Hyperion® System™ 9 BI+™ Enterprise Analytics™". Having written that paragraph with a bit more than a hint of sarcasm in the first place, I guess it could just describe the full current name without the (peevish) history. Ben White 12:15, 15 August 2006 (UTC)[reply]
  • Factual errors in User Interface section: Smart View and Visual Explorer were available before the System 9 release. TFinn734 16 August 2006
Cool -- I don't know if "robust" is the right word for SmartView though -- you can't get much more robust than the old add-in. I've edited out the comparator - I can't think of anything else better off the top of my head! Ben White 21:33, 16 August 2006 (UTC)[reply]
—Preceding unsigned comment added by 76.185.75.76 (talk) 05:09, 9 October 2008 (UTC)[reply] 

17gb vs 19.2[edit]

This line doesnt make sense to me. Saying at the same time that it is more than 17 and exactly 19.2 is a little bit strange:

If the software maps each cell as a 64-bit floating point value, this equates to a memory requirement of at least 17 gigabytes (exactly 19.2GB). — Preceding unsigned comment added by 217.111.196.16 (talk) 09:15, 17 June 2013 (UTC)[reply]

gigabytes/gibibytes resolved. Pesec.il (talk) 18:32, 4 April 2023 (UTC)[reply]

External links removed[edit]

Why are the external links removed by @Mean as custard on 2023-02-06? Pesec.il (talk) 18:36, 4 April 2023 (UTC)[reply]

They answered:
I am guided by Wikipedia:External links. I did not remove the main link to the product in the infobox. Pesec.il (talk) 17:13, 30 May 2023 (UTC)[reply]

Naming myth[edit]

On July, 2020 there was a correction for the naming myth that Essbase name derives from "extended spreadsheet database".

Since the internet is full with this derivation, shall we better claim that this is a myth?

(https://www.tapatalk.com/groups/essbase/viewtopic.php?p=46668#p46668) — Preceding unsigned comment added by Pesec.il (talkcontribs) 05:51, 15 August 2023 (UTC)[reply]

History[edit]

Shall we better extract all the historical naming for products (Hyperion Analytics etc), DB2 OLAP in a separate section?