Sometimes there are unexpected errors and it’s always fun to find the cause of them. In this blog, we would learn about fixing an error which I received while doing create catalog from SQL Server Management Studio.
On May 25, 2018, European privacy law is going to enforce new global standards for privacy rights, security, and compliance. This new regulation is known as GDPR – General Data Protection Regulations. Lots of users who are using SQL Server often wonder How to make SQL Server GDPR compliance? Before you read this blog post, I suggest you read my earlier blog post about here which explains everything about GDPR. This blog post we will take about Authentication in SQL Server (Windows and Mixed Mode) which is for GDPR Article 25.
Microsoft has recently announced a very interesting feature for security of your SQL Server. I really loved this new feature – SQL Vulnerability Assessment. Unlike most of the other V1 features which MS releases, this time I really liked this particular feature. This feature not only provides the assessments but also the solutions.
Earlier I wrote a blog about DBA doing detective work. SQL SERVER – Why We have an Audit, Trace in DATA Folder? What are These Files?. Now today there is another similar situation where the account is added automatically in SQL Server used by SharePoint.
Yesterday I shared a blog post where I discussed how to list all the users with the System Admin (sysadmin) rights. I have received a quite a few emails and comments on this subject. The comment which got the most attention is from SQL Expert Chris Mangrum. He has shared a very interesting script with modification from the original script where he has also included additional permission of Control Server.
One of the pre-requesting of Comprehensive Database Performance Health Check is to check if user has necessary system admin rights or not. It is almost impossible to help customer with SQL Server Performance if they do have a DBA who has access to system admin rights.