Naming conventions for datamart columns

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

mmiikkee@att.net - 02 May 2006 17:39 GMT

Can someone direct me to a definative source to explain or suggest
naming datamart or summary tables? Given a column in a detail table
like revenue, customer no, date (e.g., revnu,cust_no, and trans_dt) and
I create a summary table "sales summary by year_and month"
) of total customers, total revenue, month of revenue as e.g., year_mo
,cust_cnt, and tot_revnu o r summary_yr_mo,cust_cnt, and revnu.
Notice revnu is the same name.
I guess if the data dictionary defines revnu as "the amount in dollars
collected from the customer less taxes" does the table need a different
column name like mo_revnu_summ.
and then a more explicit definition. Take it further and also have a
table of the yearly totals:
summary_yr, cust_cnt,revnu or summary_yr, yr_cust_cnt, yr_revnu_summ,
and so on?
Quarterly? My thinking was to be most explicit and let user's create
their own "as" names ( for reports and stuff). Thanks. I'll look
forward to any comments.

Reply to this Message

Kiran Nair - 03 May 2006 07:27 GMT

This redbook will be useful for you

http://www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/sg247138.html?Open

Following is the summary
"
In this IBM Redbook we describe and demonstrate dimensional data
modeling techniques and technology, specifically focused on business
intelligence and data warehousing. It is to help the reader understand
how to design, maintain, and use a dimensional model for data
warehousing that can provide the data access and performance required
for business intelligence.

Business intelligence is comprised of a data warehousing
infrastructure, and a query, analysis, and reporting environment. Here
we focus on the data warehousing infrastructure. But only a specific
element of it, the data model - which we consider the base building
block of the data warehouse. Or, more precisely, the topic of data
modeling and its impact on the business and business applications. The
objective is not to provide a treatise on dimensional modeling
techniques, but to focus at a more practical level.

There is technical content for designing and maintaining such an
environment, but also business content.

For example, we use case studies to demonstrate how dimensional
modeling can impact the business intelligence requirements for your
business initiatives. In addition, we provide a detailed discussion on
the query aspects of BI and data modeling. For example, we discuss
query optimization and how you can determine performance of the data
model prior to implementation. You need a solid base for your data
warehousing infrastructure . . . . a solid data model.
Table of Contents

Chapter 1. Introduction
Chapter 2. Business Intelligence: The destination
Chapter 3. Data modeling: The organizing structure
Chapter 4. Data analysis techniques
Chapter 5. Dimensional model design life cycle
Chapter 6. Some modeling considerations
Chapter 7. Case Study: Dimensional model development
Chapter 8. Case Study: Analyzing a dimensional model
Chapter 9. Managing the metadata
Chapter 10. SQL query optimizer: A primer
Chapter 11. Query optimizer applied

> Can someone direct me to a definative source to explain or suggest
> naming datamart or summary tables? Given a column in a detail table
[quoted text clipped - 13 lines]
> their own "as" names ( for reports and stuff). Thanks. I'll look
> forward to any comments.

Reply to this Message