![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a cube created that looks at some metrics from a customer's database. All fine and good, except it catches ALL the data in the DB, when what I actually want is just the data in the last 7 days. Is there a way to design the cube to grab only this data? If it takes a little longer to process it shouldn't be a problem, as we are going to schedule it to process late at night. Thanks. |
#3
| |||
| |||
|
|
I have a cube created that looks at some metrics from a customer's database. All fine and good, except it catches ALL the data in the DB, when what I actually want is just the data in the last 7 days. Is there a way to design the cube to grab only this data? If it takes a little longer to process it shouldn't be a problem, as we are going to schedule it to process late at night. Thanks. |
#4
| |||
| |||
|
|
using the entreprise edition, you can create partitions. 1 partition for the history, 1 partition by month (or week) for the current year. then you can process 1 partition only instead of everything. the standard edition don't support the partitions. in this casem you can use the incremental loading. you do a standard process of the cube, and, every day (or week...), you'll do an incremental process to add only new rows in the cube (but don't send 2 times the same rows, this cause the value to be counted2 times) you have to keep the last date/time sent in the cube and when you'll do the incremental process you'll execute a query like select * from table where insertdate > lastdate "Wannabe_Kiwi" <amkessel (AT) gmail (DOT) com> wrote in message news:1154019577.059490.124390 (AT) p79g2000cwp (DOT) googlegroups.com... I have a cube created that looks at some metrics from a customer's database. All fine and good, except it catches ALL the data in the DB, when what I actually want is just the data in the last 7 days. Is there a way to design the cube to grab only this data? If it takes a little longer to process it shouldn't be a problem, as we are going to schedule it to process late at night. Thanks. |
#5
| |||
| |||
|
|
They're using SQL Analysis 2000 Enterprise Edition, by the way. The view idea I will keep in mind, but I don't want to add the extra load to the server. Partitions is where I'm thinking. Is there a way to do a logical window as opposed to the static ones I see in the Analysis Manager (e.g. one partition each for week1, week2, etc)? Thanks! Jéjé wrote: using the entreprise edition, you can create partitions. 1 partition for the history, 1 partition by month (or week) for the current year. then you can process 1 partition only instead of everything. the standard edition don't support the partitions. in this casem you can use the incremental loading. you do a standard process of the cube, and, every day (or week...), you'll do an incremental process to add only new rows in the cube (but don't send 2 times the same rows, this cause the value to be counted 2 times) you have to keep the last date/time sent in the cube and when you'll dothe incremental process you'll execute a query like select * from table where insertdate > lastdate "Wannabe_Kiwi" <amkessel (AT) gmail (DOT) com> wrote in message news:1154019577.059490.124390 (AT) p79g2000cwp (DOT) googlegroups.com... I have a cube created that looks at some metrics from a customer's database. All fine and good, except it catches ALL the data in the DB, when what I actually want is just the data in the last 7 days. Is there a way to design the cube to grab only this data? If it takes a little longer to process it shouldn't be a problem, as we are going to schedule it to process late at night. Thanks. |
#6
| |||
| |||
|
|
They're using SQL Analysis 2000 Enterprise Edition, by the way. The view idea I will keep in mind, but I don't want to add the extra load to the server. Partitions is where I'm thinking. Is there a way to do a logical window as opposed to the static ones I see in the Analysis Manager (e.g. one partition each for week1, week2, etc)? Thanks! Jéjé wrote: using the entreprise edition, you can create partitions. 1 partition for the history, 1 partition by month (or week) for the current year. then you can process 1 partition only instead of everything. the standard edition don't support the partitions. in this casem you can use the incremental loading. you do a standard process of the cube, and, every day (or week...), you'll do an incremental process to add only new rows in the cube (but don't send 2 times the same rows, this cause the value to be counted 2 times) you have to keep the last date/time sent in the cube and when you'll do the incremental process you'll execute a query like select * from table where insertdate > lastdate "Wannabe_Kiwi" <amkessel (AT) gmail (DOT) com> wrote in message news:1154019577.059490.124390 (AT) p79g2000cwp (DOT) googlegroups.com... I have a cube created that looks at some metrics from a customer's database. All fine and good, except it catches ALL the data in the DB, when what I actually want is just the data in the last 7 days. Is there a way to design the cube to grab only this data? If it takes a little longer to process it shouldn't be a problem, as we are going to schedule it to process late at night. Thanks. |
![]() |
| Thread Tools | |
| Display Modes | |
| |