This continues my series on auditing SQL Server. The fist parts covered discovery and documentation, server level hardware audits and SQL Server engine level audits. This section examines database configuration audits.
2024-09-18
2024-02-21
409 reads
This trigger will work even if you don't have the primary key on any table. Mechanism to configure the primary key in config table has been provided. This can be very helpful to solve the system audit requirements without much efforts.
Disclaimer : Audit Log trigger has performance overhead. It’s meant for table which is not frequently updated, deleted or inserted. Please take precaution when creating the trigger on the table having too many columns.
2019-10-15 (first published: 2019-10-10)
3,097 reads
2018-01-26 (first published: 2018-01-18)
12,344 reads
By Steve Jones
This month we have a new host, James Serra. I’ve been trying to find...
By HeyMo0sh
As a DevOps professional, I’ve seen firsthand how cloud costs can quickly spiral out...
By Steve Jones
AI is everywhere. It’s in the news, it’s being added to every product, management...
Hi, ssms is free here. I can think of other reasons to do this...
I've written some documentation on using different Markdown types of files on GitHub. It's...
Comments posted to this topic are about the item Not Just an Upgrade
I am doing development work on a database and want to keep a backup so I can reset my database. I make some changes and want to restore over top of my changes. When I run this code, what happens?
USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO USE DNRTest GO CREATE TABLE MyTest(myid INT) GO USE master RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACESee possible answers