dbTalk Databases Forums  

Filtering vs. Partitioning

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


Discuss Filtering vs. Partitioning in the microsoft.public.sqlserver.olap forum.



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

Default Filtering vs. Partitioning - 05-20-2005 , 06:13 PM






I'm considering the following three ways of partitioning our cube into
months (months of activity):

1. Filter on the date - Example: Date >= '1/1/05' and Date < '2/1/05'
2. Slice on the date - Example: Date.2005.Jan-05
3. No filter or slice: Restrict the date with a view over the fact table
(fact table is not partitioned)

What are the pros and cons are doing both? What would you guys recommend?

Thanks in advance!



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

Default Re: Filtering vs. Partitioning - 05-21-2005 , 08:31 AM






to create a parition in a cube, you have to select the target slice (which
is a month) + an SQL where statement (or the usage of another table from the
database instead-of the fact table)

The point 1 you describe is the "where" SQL statement to filter the source
table during the partition process.
The point 2 is the target slice of the cube.
so you have to use the point 1 & 2 in order to create your partition.


"Jesse O" <jesperzz (AT) hotmail (DOT) com> wrote

Quote:
I'm considering the following three ways of partitioning our cube into
months (months of activity):

1. Filter on the date - Example: Date >= '1/1/05' and Date < '2/1/05'
2. Slice on the date - Example: Date.2005.Jan-05
3. No filter or slice: Restrict the date with a view over the fact table
(fact table is not partitioned)

What are the pros and cons are doing both? What would you guys recommend?

Thanks in advance!





Reply With Quote
  #3  
Old   
Jesse O
 
Posts: n/a

Default Re: Filtering vs. Partitioning - 05-22-2005 , 01:20 AM



got it!


"Jéjé" <willgart (AT) BBBhotmailAAA (DOT) com> wrote

Quote:
to create a parition in a cube, you have to select the target slice (which
is a month) + an SQL where statement (or the usage of another table from
the database instead-of the fact table)

The point 1 you describe is the "where" SQL statement to filter the source
table during the partition process.
The point 2 is the target slice of the cube.
so you have to use the point 1 & 2 in order to create your partition.


"Jesse O" <jesperzz (AT) hotmail (DOT) com> wrote in message
news:%23t%2349FZXFHA.3840 (AT) tk2msftngp13 (DOT) phx.gbl...
I'm considering the following three ways of partitioning our cube into
months (months of activity):

1. Filter on the date - Example: Date >= '1/1/05' and Date < '2/1/05'
2. Slice on the date - Example: Date.2005.Jan-05
3. No filter or slice: Restrict the date with a view over the fact table
(fact table is not partitioned)

What are the pros and cons are doing both? What would you guys recommend?

Thanks in advance!







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.