Jules Bohanon, Lakeland, Florida:
Singular. I name tables Customer_T and Order_T instead of tblCustomer because I prefer to have them in alphabetical order. I use State_lu and City_lu for lookups.
Assem Bayahi, Mourouj 1, Tunisia:
Sometimes, mainly when working with a framework or a cms, you are obliged to respect the framework rules. But if I have the choice, based on the MVC logic, I prefer Singular names.
Md. Obaidul Haque Sarker, Dhaka, Bangladesh:
A table contains one or more tuples/rows/records. Each row means a single entity.
For example, Student information management database contain the student profile. Each student is a single entity. But all students information are stored in a table called Students. Here “Students” is a table name, and which is plural. But if a table contains only one record, it will be singular form.
Ehtisham Rasheed, Sialkot, Pakistan:
Tables names: Singular (recommended by experts)
Mark Horner, Bristol, England:
Camel casing and it depends, i.e tblEmployees or tblContactDetails etc. It’s the way I have always done it but I always make sure the table name is identifiably relevant to what it hold.
Ven Grollmus, George Town, Tasmania, Australia:
I give my Table names et al a singular name, as they are relating to an entity (ie Person). Yes a table can hold people, but at any point in time on the screen, the user is usually interacting with a single record.
Bruce Bray, Phoenix, Arizona:
I name all of my tables according to their functions. Examples : Customer, Invoice, Asset, AssetOwner, etc., etc.
Yuriy Sultanaev, Ufa, Russia:
always a plural Primary key table name in the singular + ID
Temitayo Ilori, Berea, Ohio:
Singular. Reasons: For consistency and convenience
Julie Hogue, Akron, Ohio:
I use plural and singular names, depending on the table. I use names with no spaces and I keep them short. A long name requires more coding time when writing VBA logic.
Grace Elaiza Seballos, Davao City, Philippines:
I do not use plural (except when it doesn't seem to sound right, like sales_order sounds better than sale_order). Table names are always in small letters. The names should be the same as the module name, but should be divided by an underscore "_". For example: The module Request for Leave. Then the table name will be "request_for_leave". Why? I just chose that every since I created my architecture in 2005. It is much easier for the architecture to integrate the Data Layer to the Business Logic layer when there is some form of standard. During those days when I was developing with a team, it would also make it easier for the team to debug the system. If the module name is Request for Leave, then think no further, the table for it is "request_for_leave".
Artiben prashantbhai S., Bhavnagar, India: