Greg Larsen continues his series and shows how user-defined roles roles can control SQL Server security.
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.
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.