>> I've read some article about naming convention and they all say don't
use number in the table name. <<
The reason for that heuristic is that it is a sign of attribute
splitting -- that is, instead of having one table to model, say,
Personnel, you have split that set over smaller tables based on some
attribute, say, office number. Personnel_001, Personnel_002, etc.
will be joined back together and have to be validated constantly. It
is often a newbie error of confusing a file (mag tapes in particular)
with tables.
>> I have to im****t 2 flat files from FTP for OLAP use. Both of these
files contain similar information, Customer data. <<
Look for what the table *is* by its nature. Your short descriptions
would lead me to guess at "CustomerDemographics" for A and
"CustomerSomething" for B, where something is what kind of data you
are getting -- purchases, survey results, etc. Oh, never use that
silly "tb-" affix on a table name (see ISO-11179); it tell us HOW the
data is stored, not what it is by its nature. Since we only have
tables in SQL, it is really redundant.
Do you have a copy of my SQL PROGRAMMING STYLE yet?
|
