dbTalk Databases Forums  

OLAP vs Pivot Table

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss OLAP vs Pivot Table in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Neil
 
Posts: n/a

Default OLAP vs Pivot Table - 02-14-2006 , 10:58 AM






Hi,

I'm new to OLAP and I'm looking into the pro's and con's. My users would
most likely use Excel 2000 to analyse the end result. So what are the main
differences, advantages, disadvantages or using OLAP vs connecting to
relational data and building a pivot table based on this?

The main ones I can see are speed and performance of analysing lots of data
very quickly. Also the ability to expose a cube which contains the business
logic and relational constraints rather than leave the end user to work these
out or worse make incorrect aggregations and assumptions.

Anything else?

Reply With Quote
  #2  
Old   
Jéjé
 
Posts: n/a

Default Re: OLAP vs Pivot Table - 02-14-2006 , 09:32 PM






there is a lot of differences
first its a server; so a central repository where the business rules are
stored and available to all users.
second the OLAP server allow you to create dimensions and hierarchies to
organize your data.
after this...
the server support the distinct coutn measure, calculated measures, virtual
cubes (to bring data from 2 cubes (or more) into 1 logical cube; providing
"cross analysis" capabilities)

the performance is better because you can preaggregate the cubes on the
server and the server cache the data on the server side.

if we talk about AS2005 there is far more improvement; but the current
pivottable don't provides a good interface to access these features. Office
12 solves this.

its just an overview.

"Neil" <Neil (AT) discussions (DOT) microsoft.com> wrote

Quote:
Hi,

I'm new to OLAP and I'm looking into the pro's and con's. My users would
most likely use Excel 2000 to analyse the end result. So what are the main
differences, advantages, disadvantages or using OLAP vs connecting to
relational data and building a pivot table based on this?

The main ones I can see are speed and performance of analysing lots of
data
very quickly. Also the ability to expose a cube which contains the
business
logic and relational constraints rather than leave the end user to work
these
out or worse make incorrect aggregations and assumptions.

Anything else?



Reply With Quote
  #3  
Old   
Neil
 
Posts: n/a

Default Re: OLAP vs Pivot Table - 02-15-2006 , 03:40 AM



Hi Jeje,

Thanks for the info. I'm on board with the benefits of storing business
logic in the cube, pre-aggregating etc

I guess the final question is how is it better for the end user from a point
of view of analysis. Is there anything you can do in the pivottable when
connecting to analysis services that you can't do when you just connect to a
couple of relational tables?

Thanks for your help


"Jéjé" wrote:

Quote:
there is a lot of differences
first its a server; so a central repository where the business rules are
stored and available to all users.
second the OLAP server allow you to create dimensions and hierarchies to
organize your data.
after this...
the server support the distinct coutn measure, calculated measures, virtual
cubes (to bring data from 2 cubes (or more) into 1 logical cube; providing
"cross analysis" capabilities)

the performance is better because you can preaggregate the cubes on the
server and the server cache the data on the server side.

if we talk about AS2005 there is far more improvement; but the current
pivottable don't provides a good interface to access these features. Office
12 solves this.

its just an overview.

"Neil" <Neil (AT) discussions (DOT) microsoft.com> wrote in message
news:4FC0F889-2DC5-4F2D-A385-8DEFC4A44485 (AT) microsoft (DOT) com...
Hi,

I'm new to OLAP and I'm looking into the pro's and con's. My users would
most likely use Excel 2000 to analyse the end result. So what are the main
differences, advantages, disadvantages or using OLAP vs connecting to
relational data and building a pivot table based on this?

The main ones I can see are speed and performance of analysing lots of
data
very quickly. Also the ability to expose a cube which contains the
business
logic and relational constraints rather than leave the end user to work
these
out or worse make incorrect aggregations and assumptions.

Anything else?




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.