Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.
Course Of The Month
7 days, 2 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Better way to handle 'auditing' columns such as created_by, created_dt, last_updated_by, last_updated_dt
Posted on 2014-11-19
Hi guys
In a previous question I made the below comment, which resulted in feedback that there are better ways to handle these values, to include splitting them into a separate table.
Points for advice on a better way to handle this.
Thanks.
Jim
In a previous question I made the below comment, which resulted in feedback that there are better ways to handle these values, to include splitting them into a separate table.
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.
Points for advice on a better way to handle this.
Thanks.
Jim
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
- +1
5 Comments
Active 7 days ago
I have implemented on couple of database servers to catch the data capture, this is inbuilt feature of sql server, which captured the data changes on TL , so it will be faster compared to triggers. In your case I realized that, you need to capture the User who made the changes too, which I am afraid, cant be done thru CDC; every thing related to the changed data can be audited thru CDC.
Active today
Change Tracking is more lightweight and can tell you when a change occurred for a given row ... but not what was changed, which CDC can do. CT can't directly tell you "who" either.
Default constraints could provide datetime and SUSER_SNAME() for created.
Default constraints could provide datetime and SUSER_SNAME() for created.
Active today
In a separate table you can add more features as for example if the operation was an Insert, Delete or Update, so you can also track deletes.
At the same table you can't track deletes and you don't have an history, only the last change.
Also, you can put the separate table in another file, filegroup or even database. I think it's a more flexible option but it always depends on the goal of the solution that you want.
At the same table you can't track deletes and you don't have an history, only the last change.
Also, you can put the separate table in another file, filegroup or even database. I think it's a more flexible option but it always depends on the goal of the solution that you want.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Let's review the features of new SQL Server 2012 (Denali CTP3). It listed as below:
PERCENT_RANK():
PERCENT_RANK() function will returns the percentage value of rank of the values among its group.
PERCENT_RANK() function value always in be…
For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function
Suggested Courses
Course of the Month7 days, 2 hours left to enroll
726 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.