Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Expert Cube Development with Microsoft SQL Server 2008 Analysis Services

You're reading from   Expert Cube Development with Microsoft SQL Server 2008 Analysis Services Design and implement fast, scalable and maintainable cubes with Microsoft SQL Server 2008 Analysis Services with this book and eBook

Arrow left icon
Product type Paperback
Published in Jul 2009
Publisher Packt
ISBN-13 9781847197221
Length 360 pages
Edition 1st Edition
Languages
Arrow right icon
Toc

Table of Contents (17) Chapters Close

Expert Cube Development with Microsoft SQL Server 2008 Analysis Services
Credits
About the Authors
About the Reviewers
Preface
1. Designing the Data Warehouse for Analysis Services FREE CHAPTER 2. Building Basic Dimensions and Cubes 3. Designing More Complex Dimensions 4. Measures and Measure Groups 5. Adding Transactional Data such as Invoice Line and Sales Reason 6. Adding Calculations to the Cube 7. Adding Currency Conversion 8. Query Performance Tuning 9. Securing the Cube 10. Productionization 11. Monitoring Cube Performance and Usage Index

Summary


In this chapter, we've discussed how to deal with some common problems we might face when designing our Analysis Services dimensions:

  • Grouping and banding members and numeric values

  • Slowly Changing Dimensions

  • Junk Dimensions

  • Ragged hierarchies

We've found that we can create new attributes on a dimension to group members and create bandings for numeric values using some simple SQL. This can have a positive impact on the user's experience. We've also found that with a bit of thought, the three different types of SCD can all be modeled satisfactorily. With ragged hierarchies we've learnt that the parent/child hierarchies are very flexible but have several problems, especially with query performance, and should be avoided where possible. We have also seen that using a regular user hierarchy and the HideMemberIf property is a better option, although not without its own limitations.

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image