Re: Excel-based Front End Reporting Tool
From: Howard Taylor [O2OLAP] (Howard.Taylor_at_no.o2olap.com)
Date: 02/05/04
- Next message: Kam: "Office web component connection problem"
- Previous message: Michael: "Re: Summing problems in my OLAP Cube"
- Maybe in reply to: Howard Taylor [O2OLAP]: "Re: Excel-based Front End Reporting Tool"
- Next in thread: MPS: "Re: Excel-based Front End Reporting Tool"
- Reply: MPS: "Re: Excel-based Front End Reporting Tool"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 5 Feb 2004 09:21:40 +0000 (UTC)
Sorry, but I need to correct a statement to the previous contribution.
Due to the different underlying architectures used by the products in
question, there will "probably" always be different ways each of the
products handle certain issues, each catering for their own architecture and
trying to get the best combination of both ease of use and performance. It
will be interesting seeing the products adapt to market developments and
increasing functional demands from both users and developers. Only time will
tell.
Unless there have been developments over the last few years that I am not
aware of, differences include:
1 .The treatment of multiple hierarchies, these being addressed in a
different manner by the products in questions.
2. The treatment of non-unique members and non-unique captions.
3. Writeback and how this is dealt with. There are various issues here and
the architectures handle this differently.
I will not be contributing further to this thread.
Howard
"Howard Taylor [O2OLAP]" <Howard.Taylor@no.o2olap.com> wrote in message
news:bve8ds$dud$1@sparta.btinternet.com...
> John
>
> I am going to have to differ with both yourself and Mark on this and say
> that writeback works fine and there are techniques far in advance of both
> TM1, Alea and another well know OLAP product as detailed in a previous
> thread. For the record, below is a quote from an experienced OLAP user
that
> REPLACED XLCubed and that comes from one of the environments you mention.
>
> "I have been working with Howard Taylor of O2OLAP closely since installing
a
> Microsoft Analysis Services based management information solution at my
> company. We chose O2OLAP as our data browser because it offered the most
> user friendly and flexible interface. It enabled us to create the complex
> models we needed with ease and gives the rapid response times expected
from
> a modern management information system. The views in particular make it
> possible to carry out large and complex queries extremely rapidly on cubes
> in excess of 10 million records. Anyone looking for an Excel browser for
> their Microsoft Analysis Services solution would do well to look at
O2OLAP."
>
> There is no reason to be on any other platform other than an Microsoft
> Analysis Services platform and why would anyone want to tie their
> information and modelling into a platform that is closed with its MDX
> equivalent functionality. I do agree with you that things are going to get
> better with Yukon and having seen Yukon and asked all the relevant
questions
> to the right people, all that can be done in the two products you detail
can
> get done on the Microsoft platform, but with quite a lot of other
benefits.
>
> There are also other developments in the market that have been announced
> over a week ago that are fairly crucial for solutions and how you approach
> them.
>
> Regards
> Howard.Taylor@ domain below.
> www.o2olap.com
>
>
> "John Keeley" <duvinrouge@servihoo.com> wrote in message
> news:542fe31c.0401290224.40b9da4b@posting.google.com...
> > I haven't yet seen Microsoft's new Excel offering.
> > However, I'm inclined to agree with Mark that it is unlikely to be in
> > the same league as Plain or XLCubed.
> > It will take Microsoft a few years yet I suspect.
> >
> > There still remains an important point to remember.
> > That is, Analysis Services isn't great for planning.
> > Complex business models are much easier to build with TM1 & Alea OLAP
> > platforms.
> > Writeback can still cause problems with AS compared to TM1 & Alea.
> >
> > So if you want to do serious planning (& most organisations need to)
> > you may not opt for AS or you may need Alea & AS OLAP platforms.
> >
> > The advantage Plain has is you can create dynamic reports that
> > reference both Alea & AS platforms.
> > To the end user this is seamless.
> > You get the best of both worlds: AS strength as the OLAP of choice
> > sitting on top of a datawarehouse; & Alea's strength as a planning
> > platform.
> >
> > And AS isn't going to get much better at planning in the Yukon release
> > either.
> >
> > Regards,
> >
> > John
> >
> > www.johnkeeley.com
>
>
>
- Next message: Kam: "Office web component connection problem"
- Previous message: Michael: "Re: Summing problems in my OLAP Cube"
- Maybe in reply to: Howard Taylor [O2OLAP]: "Re: Excel-based Front End Reporting Tool"
- Next in thread: MPS: "Re: Excel-based Front End Reporting Tool"
- Reply: MPS: "Re: Excel-based Front End Reporting Tool"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|