MSSQL Server DBA, Pharm.D., dog sports fanatic. All tweets are my own.
Baltimore, MD
Joined September 2013
- Tweets457
- Following202
- Followers290
- Likes855
Had a great time visiting the parents and soaking up some sun for a few days. Now it’s time to head home.
Excited to be speaking this weeekend at @SQLSaturdayDC on TempDB Performance Bottlenecks
Kat Edrington retweeted
Let’s cancel this idea that “strong people” are stoic and unfeeling. The strongest people I know are those who haven’t allowed hardship or trauma to extinguish their sense of whimsy, their capacity for hope and their ability to love.
The afternoons productivity may have just hit an all time low. The office Thanksgiving was very good. But now I think I need a nap.
A SQL audit has many options, I tend to start with Logins, Changes to users, permission changes, Schema Changes, Restart of the SQL services, Changes or stops of the Audit. From there it can depend on your use case. You can audit all the way down to access to specific tables
The SQL error Log and agent log will give you some information and you can add a limited information like logins to it. But configuring a SQL Audit, that can be sent into the SIEM will give you more useful information.