dbTalk Databases Forums  

"Optimize Schema" Wizard -- Where Does UnJoined Data Come From?

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


Discuss "Optimize Schema" Wizard -- Where Does UnJoined Data Come From? in the microsoft.public.sqlserver.olap forum.



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

Default "Optimize Schema" Wizard -- Where Does UnJoined Data Come From? - 12-09-2003 , 06:56 PM






When we use the Optimize Schema tool in the cube editor, a number of joins
between the fact table and the dimension tables are eliminated during
processing.

The SQL statements generated during cube processing (and Profiler shows no
other SQL statements being generated) seem to use only the fact table, with
no joins. However, detail from the dimension tables show in the cube -- but
we didn't join those to the fact tables!

From where is the dimension detail coming if we don't join to tables
(dimension) that contain the details?

TIA






Reply With Quote
  #2  
Old   
Deepak Puri
 
Posts: n/a

Default Re: "Optimize Schema" Wizard -- Where Does UnJoined Data Come From? - 12-09-2003 , 11:59 PM






"Optimize Schema" only applies to Shared Dimensions, and these are
processed separately from a cube by the Analysis Server. At that time,
the server stores necessary dimension detail info, which is identified
by unique member keys.

SQL Server BOL explain it this way:

http://msdn.microsoft.com/library/de.../en-us/olapdma
d/agoptimizing_1qr7.asp
Quote:
...
During dimension processing, the Analysis server creates an internal
representation of the dimension data and hierarchy. When processing a
cube, the dimension member keys identified in the member key column
property are used to access the information in the internal
representation of the processed dimension. Under certain conditions, the
dimension member's foreign key in the fact table can be used for this
lookup, thereby eliminating the need to join the dimension table to the
fact table in the database query. This significantly reduces the
complexity of the query, the amount of data accessed in the relational
database, and network traffic between the Analysis server and the
relational database.
...
Quote:

- Deepak

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!


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

Default Re: "Optimize Schema" Wizard -- Where Does UnJoined Data Come From? - 12-12-2003 , 07:39 AM



Deepak, that is an excellent answer.

Thank you so much.


"Deepak Puri" <deepak_puri (AT) progressive (DOT) com> wrote

Quote:
"Optimize Schema" only applies to Shared Dimensions, and these are
processed separately from a cube by the Analysis Server. At that time,
the server stores necessary dimension detail info, which is identified
by unique member keys.

SQL Server BOL explain it this way:

http://msdn.microsoft.com/library/de.../en-us/olapdma
d/agoptimizing_1qr7.asp

..
During dimension processing, the Analysis server creates an internal
representation of the dimension data and hierarchy. When processing a
cube, the dimension member keys identified in the member key column
property are used to access the information in the internal
representation of the processed dimension. Under certain conditions, the
dimension member's foreign key in the fact table can be used for this
lookup, thereby eliminating the need to join the dimension table to the
fact table in the database query. This significantly reduces the
complexity of the query, the amount of data accessed in the relational
database, and network traffic between the Analysis server and the
relational database.
..



- Deepak

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!



Reply With Quote
  #4  
Old   
Carl Rabeler
 
Posts: n/a

Default Re: "Optimize Schema" Wizard -- Where Does UnJoined Data Come From? - 12-15-2003 , 10:01 AM



Also check out the Analysis Services Performance Guide - we explain the
optimize schema feature in some detail in this paper.
http://www.microsoft.com/technet/tre...e/ansvcspg.asp

HTH
Carl


"Rick" <b@b.net> wrote

Quote:
Deepak, that is an excellent answer.

Thank you so much.


"Deepak Puri" <deepak_puri (AT) progressive (DOT) com> wrote in message
news:u6eSULuvDHA.2000 (AT) TK2MSFTNGP11 (DOT) phx.gbl...
"Optimize Schema" only applies to Shared Dimensions, and these are
processed separately from a cube by the Analysis Server. At that time,
the server stores necessary dimension detail info, which is identified
by unique member keys.

SQL Server BOL explain it this way:

http://msdn.microsoft.com/library/de.../en-us/olapdma
d/agoptimizing_1qr7.asp

..
During dimension processing, the Analysis server creates an internal
representation of the dimension data and hierarchy. When processing a
cube, the dimension member keys identified in the member key column
property are used to access the information in the internal
representation of the processed dimension. Under certain conditions, the
dimension member's foreign key in the fact table can be used for this
lookup, thereby eliminating the need to join the dimension table to the
fact table in the database query. This significantly reduces the
complexity of the query, the amount of data accessed in the relational
database, and network traffic between the Analysis server and the
relational database.
..



- Deepak

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!





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.