Data Cleaning - replacing nulls and addresses

Addresses in Customer Dimension

As part of an Orders dimensional model, I am attempting to design the Customer Dimension table. The customers have multiple sold-to addresses and multiple ship-to addresses. While the OLTP allows any Order to have any combination of sold-to and ship-to

Customer addresses in a high volume retail environment

I have a requirement to start capturing addresses in our data warehouse for detailed analysis of customer returns. Up until now, analysis at postal code has been sufficient. The company I work is mail order, so the addresses I need to record

How to manage nulls in Fact talble

Hello, I am new with data warehousing. I need some help with following questions 1. should the nulls be left as nulls in fact table or should they be replaced with some number that might never be used like -7 or -1. If they should be replced with -1/-

null values best practice digest

Hi all, i read all the post and design tips about null values management. Can you tell m if the following statements are right or wrong for you : Dimension attributes null values management : For string dimension attributes, use : "Not

NULLs in source lead to duplicates in Fact table

Hi, my historic source data has inconsistencies. I have a product with a 1:m to product_detail which has a 1:m to invoice which has a 1:m to invoice detail. Invoice_detail is the grain of my fact table, but some of the historic data has nulls in the lin

Some Practical Challenges

Hi All I am facing some challenges in my dimensional modeling and most of these are covered in many books too.But i have practical limitation for that 1st Challenge :Unbalanced Hierarchy In one of the dimension we are tracking employees and their

General Discussions cleaning

Hello. As you had maybe noticed, today the GD section has been cleaned out. Indeed there were a lot of old topics. As you may also notice, all the topics "Do you speak..." have been deleted (except the French one) : - Hindi - Greek -

Real time datawarehouse replacing operational reporting

Hi, As I was reading through articles I came across one of the advantages in real time datawarehouse that it can replace the operational reporting so there is no need for reports to go across 2 reporting DB there can be one centralised Real time DW and

Data Warehouse with high data availability

When a data warehouse is being updated by periodical ETL load, there could be significant performance impact on the end users' reports while the underlying tables are touched. The data becomes volatile and the query results could be different between

Data Warehousing Vendors (Manufacturing)

Dear Sir or Madam We are a local company located in Syria, specialized in Industrial Confectionary Development (Food; Biscuit, Chocolate and Juice) The company seeks to find consultants/ vendors in order to initiate a data warehouseing project to be

Reasons to use a 3NF design over a Dimensional Model design for an EDW - Discussion

I've been dimensional modelling for well over 10 years, and strongly held the opinon that only a dimensional model would work for an EDW, however i'm now begining to think that there are certain requirements that lead to a 3NF design for an 'Enterprise

Data Vault v's Dimensional Model

Seems to be a lot of interest over at LinkedIn around the DataVault model. I wondered what the thoughts were about it. When would you use it v's a Dimensional Model or even a 3NF for a data warehouse. more info here:

ETL from Oracle to SQL Server 2008 Data Warehouse

Hello, Our data warehouse runs on SQL 2008 servers. One of the transactions systems we have runs on an Oracle database and managed by a separate team. What are the recommended methods to extract source data from an Oracle database and loading to a