What's your naming convention for DATETIME posts (during my situation, using MS SQL Server)

For any column that stores once the row was produced CreatedDatetime is sensible, or LastModifiedDatetime.

However for an easy table, let us say one known as Event, can you create posts known as:

EventID,                 // Primary key
EventDatetime,           // When the event is happening
EventEnabled             // Is the event is on


ID,                      // Primary key
Datetime,                // When the event is happening
Enabled                  // Is the event is on

If you would use neither convention: Please supply the column title you would employ.

I normally title DATETIME posts as action_word_on: created_on, completed_on, etc.

The action_word defines exactly what the column signifies, and also the suffix (_on) signifies the column signifies time.

Other suffixes (as well as prefixes) might be accustomed to specify the information type (_at, _UTC, when_, etc).

Be descriptive remain consistent.

The title should communicate what Business concept of the information is incorporated in the column... "DateTime" is only the Kind of the information. Could it be once the event happened? if this was recorded? if this was saved within the DB? Once the data was last modified?

Whether it effectively conveys this is of the items the column consists of, the title is okay. "DateTime" isn't fine. "EventDateTime" is just a little better. When the table holds occasions, then any datetime area within the table is definitely an EventDateTime (It records some datetime associated with the big event). Although if there's only one datetime column within an "Occasions" table, then EventDateTime suggests it's once the event happened, so that's most likely ok.

Choose or choose the title therefore it conveys the meaning from the value...

Given edited question, some recommended names may be:

Happened, or OccurredDateTime, or OccurredUTC, (or OccurredLocal), or, if occasions inside your business design have duration, then possibly StartedUtc, or BeganUtc, or InitiatedUtc, etc.

Why refer to it as EventDateTime, whenever you don't also employ EventIDInt, or EventEnbaledVarchar? Why inlcude the information enter in the column title? (My guideline is, if they are being able to access data inside a table, they better understand what the column data types are, 'cause otherwise they do not know what they are dealing with.)

Nowadays I favor things i think about as descriptive column names, for example:
CreatedOn (if there is no time portion)
AddedOn (may be semanitcally appropriate, with respect to the data)

Selecting a "label" and taking advantage of it consistantly in each and every table that needs that sort data is another positive thing. For instance, getting a "CreateDate" column in (almost) every table is okay, because then you'll always know which column in each and every table will explain whenever a row was produced. Do not get stuck using the "but every one has to possess unique names" argument if you are writing a question, you ought to know which tables you are tugging each column from.


I simply remembered the best I have done previously. If your DateTime (or SmallDateTime) column will contain virtually no time portion, only the date, like a "indication" I'd put "Date" within the column title, for example "BilledDate" rather than "Charged" or "BilledOn". This should not apply when monitoring when rows were added, since you will want time too.

I'd stay away from datatypes for column names (a DATETIME column known as Datetime), and so i election for that first option.

I favor to produce posts within the second form--although I'd most likely desire a more informative title than Datetime, based on what its use could be.

Edit: Within this kind of situation, I would really opt for a hybrid for your single area, making it 'EventDate', 'StartDate', or something like that similar.

I'd likely use something similar to "WhenRaisedUtc".