﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Data Warehousing / Strategies and Ideas  / Unknown dimension values or / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Mon, 20 May 2013 10:23:21 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Unknown dimension values or</title><link>http://www.sqlservercentral.com/Forums/Topic1380754-363-1.aspx</link><description>I like the idea of unknown versus undefined at source.  I stay away from using zero (although I have done so in the past), as zero is often a valid value.  If you're using a true surrogate key, then that's not an issue, but often we muddy the waters by using a natural key (such as using time for a time dimension, and zero may well be a valid time).I model in the relational DW, and then project that into SSAS, rather than model in SSAS.  I guess if you model directly in SSAS without a relational DW, then you may do that there and not worry so much about it.</description><pubDate>Wed, 21 Nov 2012 11:54:01 GMT</pubDate><dc:creator>Bruce W Cassidy</dc:creator></item><item><title>RE: Unknown dimension values or</title><link>http://www.sqlservercentral.com/Forums/Topic1380754-363-1.aspx</link><description>I tend to use -1 with Unknown as the description, and occasionally also use -2 with Undefined at Source. The two are very different especially when loading data from 2 or more systems and conslidating them, where System one might have an value where system two doesnt recognise that particular field and theres no mapping. </description><pubDate>Thu, 08 Nov 2012 08:21:57 GMT</pubDate><dc:creator>Jason-299789</dc:creator></item><item><title>RE: Unknown dimension values or</title><link>http://www.sqlservercentral.com/Forums/Topic1380754-363-1.aspx</link><description>I [i]always[/i] have an unknown in a dimension, and it's key is 0.  Then the sql statements can be COALESCE(value, 0).  Most of the time using 0 is not an issue, but occassionally it makes it problematic.  Not such a problem that I regret doing it that way.I often has an N/A dimension, and it's key is -1.  There is only an N/A when it makes sense.  So Creation Date does not have an N/A.  An open order has N/A for complete date.  A completed order that for some reaons doesn't have a date would be classed as Unknown.I'm not sure how setting the unknown value will work, so I can't compare the two.  It maybe that I'm using old fashioned methods, or it may be that my desire for the greater control is a good thing.  It would be interesting to hear from someone who has done both.</description><pubDate>Tue, 06 Nov 2012 07:10:57 GMT</pubDate><dc:creator>RonKyle</dc:creator></item><item><title>RE: Unknown dimension values or</title><link>http://www.sqlservercentral.com/Forums/Topic1380754-363-1.aspx</link><description>Unknown, Not Applicable, ...I think these allow you more control over the design and data loading.</description><pubDate>Mon, 05 Nov 2012 10:50:34 GMT</pubDate><dc:creator>PMwar</dc:creator></item><item><title>Unknown dimension values or</title><link>http://www.sqlservercentral.com/Forums/Topic1380754-363-1.aspx</link><description>In your DW do you always create an "-1 Unknown" record for each dimension?  For example in DimEmployee:[code="plain"]EmployeeKey -1EmployeeName "Unknown"ect.[/code]Or do you just rely on setting SSAS's UnknownMember and UnknownMemberName properties?[url]http://technet.microsoft.com/en-US/library/ms170707%28v=sql.105%29.aspx[/url]Just curious what other folks do.Thanks,Rob</description><pubDate>Sat, 03 Nov 2012 17:44:31 GMT</pubDate><dc:creator>robert.gerald.taylor</dc:creator></item></channel></rss>