SSAS Tips

Microsoft SQL Server Analysis Services 2005/2008 Tips

Here you will find collection of the short tips that will help you use SSAS more efficient.
Filter     Display # 
# Article Title
1 To get a comma separated list of members for dimension attribute use following mdx
2 Use BIDS 2008 to validate Analysis Services 2005 cubes
3 Relationship between fact dimension could have type "Fact relationship" or "Regular relationship". No difference, except metadata
4 Speed up MDX query preparation in Reporting Services by specifying default parameter value
5 Set proper InstanceSelection property for attributes used in the Report Model with Lookup Entity
6 You can order date dimension in descending order by setting OrderByAttribute property
7 Process only one partition so you can browse the cube
8 Using unformatted cell values it may improve query performance
9 NULL default measure might improve querying performance
10 Split large partitions, with more than 20 million rows or that are over 250 MB in size, into ...
11 Set the Slice property on partitions with ROLAP storage mode or with proactive caching settings...
12 Remove aggregation designs that are not used by any partitions
13 Limit the number of aggregation designs in a measure group to three
14 For partitions, do not use proactive caching with a polling query but no processing query
15 Consolidate partitions for measure groups with 5 or more partitions that have less than 2 million...
16 Avoid specifying ROLAP storage mode or enabling proactive caching with the OnlineMode property ...
17 Do not build more that 500 aggregations for a partition
18 Design aggregations for partitions with 500000 or more rows
19 The names of attribute relationships should match the names of the related attributes
20 Create hierarchies in non-parent child dimensions
21 Avoid visible attribute hierarchies for attributes used as levels in user-defined hierarchies
22 Set the AttributeHierarchyVisible property for the key attribute in a parent-child dimension to Fals
23 For dimensions, do not use proactive caching with a polling query but no processing query
24 Either disable the attribute hierarchy or set the AttributeHierarchyOptimizedState property to ...
25 Do not ignore duplicate key errors. Change the KeyDuplicate property of the error configuration ...
26 Define the default member for non-aggregatable attributes in either the DefaultMember property or ..
27 Define attribute relationships as 'Rigid' where appropriate
28 Change the UnknownMember property of dimensions from Hidden to None
29 Avoid redundant attribute relationships because these relationships may prevent data from being ...
30 Avoid large parent-child dimensions that have 500000 members for the key attribute
31 Avoid diamond-shape relationships not covered by hierarchies
32 Avoid defining non-aggregatable atributes in a parent-child dimension with the exception of the pare
33 Use numeric key columns for attributes with 500000 or more members
34 Design hierarchies such that lower levels have more members than higher levels
35 Avoid specifying more than one non-aggregatable attributes per dimension
36 Avoid creating hierarchies where attribute relationships do not exists between one or more levels
37 Define a time dimension
38 Avoid having 10 or more dimensions with a single attribute. Consider unifying them
39 A database should have no more than 3 parent-child dimensions that have ...
40 Define partitions for measure groups
41 Avoid non-materialized reference dimensions
42 Avoid having 15 or more measure groups in a cube
43 Avoid defining measure groups with zero dimensional overlap
44 Avoid cubes with a single dimension
45 Include the default measure of a perspective in the perspective
46 Consider setting dimensions that contain measure groups with semi-additive measures to MOLAP
47 Break distinct count measures into separate measure groups
48 Avoid defining many-to-many relationships when either the intermediate measure group ...
49 Avoid creating measure grops that have the same dimensionality and granularity
50 If you can, list in SELECT statement real measures first and calculated measures after
 
<< Start < Prev 1 2 Next > End >>
Page 1 of 2

Quick Poll - Please vote

What is the most important feature for you in the BIDS Helper utility?