Here is the list of properties that i did not find in MSAS 2005.

Dimension Properties:
---------------------------------------
- Source Table Filter
- Aggregation Usage: 'Top Level Only', 'Custom', 'Standard'

Memory Settings:
--------------------------------
- Read a head buffer setting
- Process Buffer setting

Log Files:
---------------------------------
Analysis Services Log file

Thanks,

Venkat.

Could you please clarify what you would like to advise? AS2k5 is a
completely different model than AS2k in that the latter is dimension based
while the new version is hierarchy/attribute based. Because of this shift
in model, quite a few things have changed - all for the better in my opinion
:-)

For example, Source Table Filter really goes under the paradigm of query
binding or table binding within your cube partitions. Aggregation usage has
changed quite a bit because your aggregation is not based on the dimension
any more but by the hierarchy. The memory allocation and log files are part
of the new configuration for AS2k5 - you can find them at:
http://msdn2.microsoft.com/en-us/library/ms174556

--
HTH!
Denny Lee
<dennyglee_at_hotmail_dot_com>

Blog at:: http://spaces.msn.com/members/denster/



"Prasad" <Prasad (AT) discussions (DOT) microsoft.com> wrote

Hi Lee,

Thanks for the reply.

Let me put my questions straight.

1. I have a 'time' rollup table in DB2 from which i am creating the 'Time'
dimension. The table has rows corresponding to years starting from 1990 to
2010. I just want my dimension to have years from 2001 to 2005. In MSAS 2000,
i used to do this by applying a 'source table filter' while creating the
dimension itself.

Simply tell, if there is such property that i can set to limit the content
of the dimension. I know i can create a named query instead of doing all
this. But just curious what happened to this property in MSAS 2005.

2. In MSAS 2000, in the cube editor, i would go to each dimension and mark
its 'Aggregation Usage' property to 'Top Only' if i do not want to iunclude
all the dimension levels in the aggregation strategy.

Simply, tell me the way to do this in MSAS 2005.

3. My cubes are processing dead slow in MSAS 2005 compared what they were in
MSAS 2000. I know in MSAS 2000, i had to play with 'Process buffer' & 'Read
Buffer' to improve the performance.

Were they called something else in MSAS 2005? I nned to change them to
increase the speeds.

Please let me know.

Thanks,

"Denny Lee" wrote:

DAW: Queries are very different in AS2K5. Using a named query is the right
way to do this. For partitions you could use a query binding and specify the
SQL statement directly for the partition, but you don't have that option in
a dimension. So using a named query is the right approach.

DAW: In AS2K5, you have a similar setting. You set it in the cube editor.
Make sure you are on the "Cube Structure" tab, then look in the lower
left-hand corner where the dimensions are listed. There are two tabs: one
for hierarchies; one for attributes. Make sure that you have clicked on
"attributes".

AS2K5 is an attribute-based system -- AS2K is a hierarchy-based system. Thus
aggregates in AS2K5 are kept at the "attribute"-level. Go over to each
attribute and you will see an aggregation usage property. Set it to "None"
for each enabled attribute hierarchy.

DAW: AS2K5 does this automatically for you. As you are working with DB2, I'd
start there with an analysis of the SQL statements that AS is issuing when
it processes the databases. The format of those queries quite possibly has
changed and that might be the issue with the performance findings.

--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Prasad" <Prasad (AT) discussions (DOT) microsoft.com> wrote