Avatar of brasso_42
brasso_42
 asked on

MSSQL 2012 - Date a record was added

Hi

Is there any way to find out what date a record was added to a table other than adding a date field and putting the date in there at the point of creating the record?

e.g table1
Name          Tel_No
Fred             1234
Bob              4321

How can I tell when bob was added to the table?

Thanks
Microsoft SQL Server

Avatar of undefined
Last Comment
Scott Pletcher

8/22/2022 - Mon
Phillip Burton

alter table table1
add MyDate datetime constraint rightnow default GETDATE()

Open in new window


It is not retrospective, but when add the current date and time when a new record is entered.
ASKER CERTIFIED SOLUTION
Vitor Montalvão

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Scott Pletcher

You can also log this outside of the main table itself.  I prefer that, although developers don't, in my experience.

Developers love to put all those extra columns in *every* table, but they obviously increase the row size, sometimes drastically (on some intersection tables, the create & update cols are more bytes than the actual data in the row!).  

If you're going to add these types of columns in the table itself, at least use an int id rather than varchar(), by creating a separate lookup table for the names.
Scott Pletcher

In theory, if the table uses an identity column, you could also get the date by simply capturing the id number every day at midnight, then looking up the id number to see which day range it falls into.  For more precise time, you could capture the identity value every hour, or even every minute.

Of course if the identity value gets reset you could have issues, but many tables will truly never do that because it would also destroy the app itself.  If they're truly being used, the new values would simply replace the old values in the id-->date conversion table.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
brasso_42

ASKER
Thanks for your help!
Jim Horn

Scott - I created a new question asking about the better ways to handle these 'auditing' columns, per your comments.  I'm genuinely interested in how you're currently pulling this off.  Thanks.
Scott Pletcher

I'll Monitor the new q for a while before I say anything, to allow others to present their thoughts on this.  I suspect strongly that DBAs and developers will see this q quite differently :).

Btw, I am on the DBA side, and thus against "automatically" adding ~40 bytes and two triggers to every table :).
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.