Home > Archive > MS SQL Data Warehousing > October 2006 > Server behaviour with Partitioning









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Server behaviour with Partitioning
stevefromoz

2006-10-25, 6:00 am

Assumptions: using AS2K5 ent edn; assuming no aggregations to allow me to
say 'server would read from partition' rather than aggregation.

If you were to partition a measure group by say year and state (e.g.
Store.State) resulting in maybe 50 partitions (5 years by 10 states).

When a query was to filter by "year 1", regardless of what the other
dimensions/attributes requested were in the qeury (assuming none were from
the Time dimension), the query engine should interrogate/request results
only from the partitions for each state for "year 1" ? e.g working on teh
assumption of 10 states, then the server would be required to read data from
10 partitions (one per state for that year).

Extending this, if you were to then query for a particular State in a
particular year, would you expect to see the server read only from the
partition containing this year/state combination? Would this hold true if
querying an attribute below the State level (say City)? Am assuming the
answer would be Yes as long as the attribute relationships have been
declared to show that State is a parent of City and then City is related to
the Key.

I'm seeing the behaviour described in the first query. Where I'm performing
the second type of query I'm seeing the server accessing all 10 partitions
again even though the fact data in question will reside only in 1 partition.



Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2009 droptable.com