Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

At the moment, we have a Persons Table. But we also need another table to store changes made to that Persons Table. But, my question is, what naming convention is used for tables that store changes made to other database tables.

share|improve this question

closed as primarily opinion-based by Kin, Phil, Joel Brown, Mat, Mark Storey-Smith Sep 20 '13 at 14:34

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

Auditing or Tracking. – Phil Sep 20 '13 at 12:35

In our company, we use to suffix the table name with _history. So, for the persons table you might have a table named persons_history.

share|improve this answer

This is totally dependent on opinions. There is no right or wrong answer to this question.

if you are using SQL Server, then the naming convention that I would follow is


So for storing changes made to Persons table, it will be schema_name.AUDIT_PERSONS. Make sure you are in the right database when you create the table. For sql server 2005 and up, dbo is the default schema.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.