Naming Standards
Page 1 of 1
Naming Standards
What is a good convention for tracking actual standards in the data model? For instance, we are tracking a customers "standard" codes and descriptions of results as well as industry standard codes and results. This potentially could get deeper if there is a "standard" code and description between the customer and the industry.
I was considering two tables (one for the primary standard and one for the alternate standard(s)). If the alternate had several standards, then a priority column to track usage and a description column to track which alternate standard (ie customer, regional, etc).
I was considering two tables (one for the primary standard and one for the alternate standard(s)). If the alternate had several standards, then a priority column to track usage and a description column to track which alternate standard (ie customer, regional, etc).
triton46- Posts : 1
Join date : 2011-11-21
![-](https://2img.net/i/empty.gif)
» Naming standards
» How does dimension hierarcy affect granularity?
» Naming of ID and code fields
» SQL View Creation Standards - Guidance Needed
» Table and Column Naming Conventions
» How does dimension hierarcy affect granularity?
» Naming of ID and code fields
» SQL View Creation Standards - Guidance Needed
» Table and Column Naming Conventions
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|