Hi,

I am learning Ms Sql and I found that a lot of the tables I am finding
( in different tutorials ) are using special names for their column
names such like au_username, au_salery ...
Is the any naming convention for column names, or just at all is there
any reason for naming the table columns in specific way.

Thanks in advance.

Hi

You can use
http://vyaskn.tripod.com/object_naming.htm

Although I am not a fan of extending column names to include (part of a)
table name as it should be redundant if the tables are always referenced
with the tables alias in the code. It is important to be able to easily
differentiate tables/views/functions as well as a naming consistentency and
clear code formatting.

John

<John.Arthur (AT) gmail (DOT) com> wrote

Its often personal. My preference (over 10 years of db design, and DBA) is
to use simple names with no table or type extensions.Therefore au_user
becomes user, au_salary becomes salary.

The main reason for simple naming is that end-users frequently see table and
field names and they tend to find extended naming structures confusing.

The most important thing is to be completely consistent ;-)

Hungarian (including type in name) can be more useful in programming but
even that is debatable with modern IDE's and debugging tools (IMHO)

Julian


<John.Arthur (AT) gmail (DOT) com> wrote

ISO-11179. I also have a book due out this year which gives rules for
data elment names based on that standard and which quotes a lot of
reading studies, etc.

Too bad that virtually everything given there is in violationof the
ISO-11179 standards. The guy that posted them is an OO programmer and
not a data guy at all. The basic idea of the ISO standard is to name a
thing for what it is in the Universe of discourse. This guy names
things for where they are used (table name prefixes), and for how they
are used (pk prefixes) and they are implemented (trigger, index, etc.
postfixes).