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
LVL 1
brasso_42Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Phillip BurtonDirector, Practice Manager and Computing ConsultantCommented:
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.
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Philip, that is what he don't want to do
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

You can do it reading the transaction log but for that you'll need a 3rd party software and they aren't cheap.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
imo the above two experts nailed it.  The answer is 'No you can't', although there are expensive apps to do it (Vitor's post) and ways to handle it in the future (Phillip's post).

As a general rule any table I design that has data entry, I'll add four 'auditing' columns to it that populate via INSERT and UPDATE triggers:
  created_dt  -  datetime - of the entry
  created_by_id -  varchar(30) - SUSER_NAME() of the person creating it
  last_updated_dt  -  datetime - of any insert-update
  last_updated_by_id - varchar(30) - SUSER_NAME() of the person updating it.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Scott PletcherSenior DBACommented:
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.
0
Scott PletcherSenior DBACommented:
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.
0
brasso_42Author Commented:
Thanks for your help!
0
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
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.
0
Scott PletcherSenior DBACommented:
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 :).
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.