If you are being serious in your role, then the amount of times you grant permissions to the public role should either be a) never, b) when you want to have a data breach, or c) you are testing in a sandbox to improve your skills.
This is an introductory level method demonstrating how to quickly audit database objects and principals for granted permissions.
DBAs often need to figure out who has access to what. When that need arises, it is frequently adequate to just perform a quick permissions audit.
No matter how simple the task or how versed we are with doing a security audit, it seems like we can always stand to learn just a little bit more. No matter how many times we hand an audit report over to the auditor, there is always “just one” more report we have to provide.
Some view the permissions for Extended Events as a limitation. I see the required permissions as an appropriate set and recommend all to work with XE and permissions to provide higher efficiency to their environment.
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.
Did you know that you can grant permissions down to the column level in SQL Server? Well, if you didn’t know that – you do now. It is actually rather simple to grant permissions […]
This article takes us to the edge with a couple of CRM related errors after changing the service account to a more secure Managed Service Account. Despite the CRM reports working properly within Report Manager (via SSRS), the reports would fail in CRM.
When running into error 1326, it makes plenty of sense to try to create a backup dump device (only as a testing exercise) as well as test the connectivity to the UNC path from the local server instead of a remote server.