Home/ Questions/Q 678713
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T01:10:48+00:00

If I create a table with datetime default getdate() field that is intended to

  • 0

If I create a table with datetime default getdate() field that is intended to keep date&time of record insertion, which name is better to use for that field ?

I like to use Created and I’ve seen people use DateCreated or CreateDate.

Other possible candidates that I can think of are: CreatedDate, CreateTime, TimeCreated, CreateDateTime, DateTimeCreated, RecordCreated, Inserted, InsertedDate, …

From my point of view anything with Date inside name looks bad because it can be confused with date part in case if I have 2 fields: CreateDate,CreateTime, so I wonder if there are any specific recommendations/standards in that area based on real reasons, not just style, mood or consistency.

Of course, if there are 100 existing tables and this is table 101 then I would use same naming convention as used in those 100 tables for the sake of consistency, but this question is about first table in first database in first server in first application.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I tend to InsertedDateTime and InsertedBy (and Updated%, Affected% for indirect updates perhaps, Deleted% for logical deletes).

    OperationDateTime for general auidt table

    If I was storing a date only, it would be StartDate. Likewise, time only would be BookedTime

    Another rule is to avoid "SQL" terms, so Added/Changed rather then Inserted/Updated. I inherited Inserted/Updated and it’s consistent at least

    Just be consistent: no mixing Created% with Inserted% with Added%

    • 0