Checking for Database Events Using Extended Events and SQL Monitor

You need to make sure that nobody tampers with your production databases, or really any databases outside Development. Even if you weren't of a nervous disposition, you'd want to know if a database was stopped or removed. You'd also be intrigued by the sudden unrehearsed addition of a database to a production server.

SQL Server Security Best Practices for an Application Installed on SQL Server

In this article we look at the steps you can follow to create a secure and locked down instance of SQL Server to only be used by the intended application on the same machine.

Moving a Default Schema

Introduction to SQL Server Security — Part 6

SQL Server has many tools used to make it secure. In this article, Robert Sheldon demonstrates several of these features including SQL Server Configuration Manager and the Vulnerability Assessment tool.

Introduction to SQL Server Security — Part 6

SQL Server has many tools used to make it secure. In this article, Robert Sheldon demonstrates several of these features including SQL Server Configuration Manager and the Vulnerability Assessment tool.

DBAs: Stop Denying Sysadmin to Developers

Kendra Little explains why DBAs don't allow sysadmin permissions in development, and why, it at all possible, they should.

SQL Vulnerability Assessment

SQL Vulnerability Assessment is a feature available in the latest versions of SQL Server Management Studio (SSMS). This feature is very easy to use and it will show you...

Always Use Roles–#SQLNewBlogger

Another post for me that is simple and hopefully serves as an example for people trying to get blogging as #SQLNewBloggers. Which of these is more complex? GRANT SELECT...
The...

Why am I getting an NT AUTHORITYANONYMOUS error when creating or altering a stored procedure?

If you have to deal with linked servers then you probably have or will run into the following error: Login ... Continue reading
The post Why am I getting an...

Introduction to SQL Server Security — Part 4

The sa account is the most powerful account in a SQL Server instance, and most DBAs disable it. There are several other built-in accounts that you may not think about that often. Robert Sheldon continues his SQL Server security series with an article about built-in accounts.