That which we call a rose by any other name would smell as sweet. Sometimes DP professionals, and database developers in particular, forget this. This article will provide a different approach to database naming standards by ignoring all of the basic generalizations that were foisted upon us in Database 101 class and taking a fresh look at the naming of relational database objects. The article will concentrate on DB2 objects, but the arguments made in the article are just as valid for other relational databases as well. A table consists of multiple rows, each with a fixed and unchanging number of defined columns.
Synonyms are accessible only by the synonym owner.
VIEW - an alternative representation of data from one or more tables or views. An end user need not know whether he or she is querying a table, an alias, a synonym, or a view. To the user, the results are the same - data represented by values in rows and columns. This brings us to our first revision to the common wisdom for database naming standards. Use the exact same naming convention for tables, views, aliases, and synonyms.