![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
| Project REAL: Analysis Services Technical Drilldown |
#3
| |||
| |||
|
|
Hi Jasper, I've also typically built AS 2000 cubes with separate Date and Time Of Day dimensions, but am still in the process of migration to AS 2005 (new AS 2005 cubes take precedence!). Anyway, there are some Time dimension-related best practices called out in the Project REAL technical article on Analysis Services. It seems to be endorsing the concept of a separate Time Of Day, but maybe only one (the Date dimension?) should be marked as being of the Time type. Will that work for you? http://www.microsoft.com/technet/pro.../realastd.mspx Project REAL: Analysis Services Technical Drilldown By Dave Wickert, Microsoft Corporation SQL Server Technical Article Published: September 2005 .. If your application needs a drilldown that is deeper than day, consider separating time into two dimensions. One dimension records time down to the day level and a second dimension records the time of day. .. Best Practice: If you use semiadditive measures, be sure that cubes have no more than one time dimension. There are some limitations on the use of semiadditive measures. First, you must have a dimension marked as type Time to use semiadditive measures. See Figure 25 for an example. The Time Intelligence Wizard sets the attribute and dimension type properties appropriately when it runs. If you create your time dimensions using the standard Dimension Wizard, then you must manually set the appropriate type properties. - Deepak Deepak Puri Microsoft MVP - SQL Server *** Sent via Developersdex http://www.developersdex.com *** |
![]() |
| Thread Tools | |
| Display Modes | |
| |