http://blogs.technet.com/andrew/archive/2008/05/30/using-tinyint-as-keys-in-analysis-services.aspxFact tables should be narrow and deep.&#160; If you are recording every debit card transaction for every customer across the fifteen retail banks you own, you end up with 15 million rows a day, so to save space they need to be as thin as possible.&#160;en-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.technet.com/andrew/archive/2008/05/30/using-tinyint-as-keys-in-analysis-services.aspx#3185756Mon, 19 Jan 2009 19:45:53 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3185756Marco Russo<p>There are already two open cases for this.</p> <p>I opened in 2007 this one: <a rel="nofollow" target="_new" href="https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=278682">https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=278682</a></p> <p>And this one is dated 2006:</p> <p><a rel="nofollow" target="_new" href="https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=126798">https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=126798</a></p> <p>Will the 2009 be a good year for a fix? :)</p> <p>Marco</p>