Archives of the TeradataForum
Message Posted: Fri, 28 Jun 2002 @ 16:16:28 GMT
<-- Anonymously Posted: Friday, June 28, 2002 11:05 -->
Here are my two cents on this subject:
I believe that a given data attribute should have one and only one name in the business. There are several reasons for this (and we have successfully standardised on this in our warehouse environment):
1. If the names are standard, code can be reused, code samples exchanged between different user groups, divisions etc.
2. If the nameds are standard, there only needs to be one metadata definition maintained. This makes the maintenance simpler and this may ensure that these definitions can be kept up to date.
3. Support is simpler as support personnel do not have to remember the subtleties in naming standards between marketing and finance for example.
4. Transferring of staff from one business area to another is smoother and the learning curve is not so steep!
However, for this to work, you need to ensure that a given attribute (eg account number) has the same meaning everywhere it is used. So if you have an account number type attribute that means main account number, it should be called main account number.
In addition, the data types should also be the same for all occurrences of that attribute.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|