1 DBA's Professional Blog
We all have our favorite scripts, tools or utilities. Those are the things that help make our jobs easier. In this article, I share with you a poor mans audit solution to help catch unwanted permissions changes.
One day while checking things for clients, I happened across a fun little error message – “SQL Server Audit failed to create the audit file”. It just so happens that the audit had been working and then suddenly stopped and started flooding the error logs with this message.
Why would it suddenly stop working? Well, it says in the error that the disk might be full or that there may be a permissions issue. So, at least there are some possibilities provided by the message. Granted – neither of these options is very settling for a DBA.
It is very important to understand who has what level of access within the server and databases on that server. Sometimes we see users being granted server or database access through the fixed roles available in SQL Server. How exactly do you know what permissions those individuals have via role membership? This article will help to reveal the permissions granted to the various roles and maybe a gotcha or two.
A fundamental component of SQL Server is the security layer. This article covers three common security misconfigurations in SQL Server.
What do you do when a developer comes to you and asks, “Where did the database go? The database was there one minute, and the next it was not.”
Legislation and regulation sometimes dictates that certain activities must be tracked within a database. On occasion, it will be required that queries be audited and tracked to reach compliance with the legislation or regulation. To achieve this compliance, this article will demonstrate how to use Extended Events to audit statements being executed within the database.
A fundamental component of SQL Server is the security layer. A principle player in security in SQL Server comes via principals.
The use of SQL Audit can be viable to track the changes that may be occurring within your SQL Server – from a settings point of view
No matter the mechanism used to capture the data to fulfill the “investigation” phase of the audit, if the data is not analyzed and reports generated, then the audit did not happen. With that in mind, I settled on a quick intro in how to get the audit data in order to generate reports.
One of my pet-peeves (and consequently frequent topic of discussion) is finding database settings (or any setting that has changed) without knowing about it. Worse yet is finding that the change has occurred and nobody […]