There was a time when SQL Server used to run on only Microsoft Windows. However, the time has changed and SQL Server now runs on Linux as well. This is indeed a great move as I believe database such as SQL Server should be running on multiple platforms. This is indeed a very interesting but it ads one more additional check before I jump into Comprehensive Database Performance Health Check. In this blog post, we will learn about how to get host information from OS.
SQL SERVER – How to Make SQL Server GDPR Compliance?
I am really not sure how many times I have been asked about GDPR Compliance in the recent months. You must bookmark this page and share with your organizations if you are doing business with European Union or firm based out of European Union.
It is quite often to see the email in mailbox with the following title –
How to Make SQL Server GDPR Compliance?
SQL SERVER – Activity Monitor – Active Expensive Queries
Recently during Comprehensive Database Performance Health Check, I had a very interesting conversation. SQL Server has introduced Activity Monitor many version earlier. I think everybody is now pretty familiar with this tool and use it frequently. However, during my consulting work, I use different scripts which are much more efficient than Activity Monitor. However, it is alright to use it once in a while.
SQL SERVER – How to Change Column Property From NULL to NOT NULL Value?
A Very popular question I often here whenever I am presenting at the developer conference – How to Change Column Property From NULL to Not NULL Value?
SQL SERVER – 2017 – How to Remove Leading and Trailing Spaces with TRIM Function?
TRIM Function has haunted SQL DBA for ages. If you have been using SQL Server for a while, you will totally agree with me over here. In this blog post we will see how the new feature TRIM of SQL Server 2017 works in few simple words.
SQL SERVER – Introduction to Log Space Usage DMV – sys.dm_db_log_space_usage
It has been quite a while since SQL Server 2017 has been introduced, however just recently I have been seeing interest for this project. Lots of users are just switching to SQL Server 2017 and I believe that is normal. In the year 2017 during my Comprehensive Database Performance Health Check, I encountered mostly SQL Server 2014 and SQL Server 2016. Recently, during the consultancy, I received a very interesting question about log space.




