Setting up a data warehouse connection and selecting tables
At the core of a data warehouse, there are facts and dimensions. They can be organized in star schemas, snowflake schemas; they can be more or less complex, and to some extent undocumented. This is not a book about dimensional modeling and discussing how a database layout works better than other is out of scope. Some common sense rules always apply: consistent column naming can be useful (user_id
, iduser
, user_code
, key_user
, yetanotheruserid
, you name it…), constraints on tables help to pull the strings and find a way into unexplored databases. NOT NULL
fields also come in handy.
I personally had my share of good and bad data. I always remember a development team manager who once asked ...
Get Business Intelligence with MicroStrategy Cookbook now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.