This article shows how to audit the logon events for SQL Server 2012 and beyond through the use of XEvents.
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.
This article takes a look at an error that may occur depending on your use of linked servers and the use of openrowset.
Explore how to avoid unwanted results that oft occur due to lack of attention to detail, use of internet examples, misunderstanding of the requirements; and always from granting way too much access.
With a little planning and care, we can find various ways to fulfill user requests without compromising the environment.
Planning to upgrade/migrate requires a fair amount of prep work. Some of that prep work involves auditing your server for any users that may still be using the instance.
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.
A powerful little expression in SQL Server is the CASE statement. The CASE statement has the ability to “transform” data per business rules to help better understand the data in a given query. In the simplest form, the CASE statement is a statement that evaluates a list of conditions (in order) and returns the first matching result expressions.
The defaults in the msdb database are about what is missing. It’s missing quite a few things that could be critical to your environment.
This is an introductory level method demonstrating how to quickly audit database objects and principals for granted permissions.