Our database does not have any audit functionality. It does not records who inse

Question

Our database does not have any audit functionality.

It does not records who inserts the record or who who changes it

It does not keep a history of the changes made

Nothing can be restored if something goes wrong

There are many other short comings for example the database does not have any data integrity, anything an be thrown in, no check on different fields, duplicates etc

My question is, who's job it is to put this functionality in? An ASP Developer who knows basics of SQL and who interacts with the database regularly. Or an SQL Administrator who's sole job is to work with the databases, optimize it and maintain it?

At this point we do not have an SQL Administrator, but can hire one. How big of an undertaking this should be for a developer to fix the above issues?

Explanation / Answer

This is not the job of an ASP developer or the SQL Admnin (DBA). It is the job of a database developer or database architect. If you have to you can hire a DBA to do it, but really they are generally too busy to do design.

Note it is much harder to put things like referential integrity and data checks into place once there is data in the database, this is why you should never design a database without an expert. ANd of course audit functionality will be limited to only those changes going forward, no one can recreate what happened in the past that was not recorded.

Related Questions

Navigate

• Browse (All)
• Browse O
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.