Right now, in database log setup form. Every time a new table/field got setup with database log successfully, the value of every "create by" field will mass update with latest user who had perform update on database log and the value of every "create date" field will mass update with latest time when a user had performed update on database log. This could cause customer unable to audit for particular situation. Looking forward for Microsoft to take up notice of this request and provide a fresh way to modify the logic behind database log if possible
Comments
It's a thoughtful observation to recognize the impact of the current database log setup on auditing capabilities. Your suggestion for Microsoft to consider a revision of the logic behind the database log is constructive and highlights a potential area for enhancement. It's positive to see proactive engagement in seeking improvements that could benefit the auditing process. Looking forward to seeing how this idea progresses and the innovative solutions that may emerge. Thank you for sharing your insights!
Category: System administration