During recent SQL Server Performance Tuning Practical Workshop I receive following question about Query Optimizer Fixes.
SQL Download – SQL Server Management Studio (SSMS) – Performance Dashboard
It has been quite a long time since I stopped posting about various SQL downloads available on the interest. The reason was that many users were not interested in learning about it. However the latest release of SQL Server Management Studio (SSMS), requires a mention about it. The latest version contains Performance Dashboard by default.Â
SQL SERVER – How to Build Three Part Name from Object_ID – Part 2?
Earlier this week, I posted an interesting interview question How to Build Three Part Name from Object_ID? – Interview Question of the Week #134. In its response, I have received a very interesting reply from Rin Sitah over here.
SQL SERVER – How to Convert CollationID to Collation Name?
One of my blog readers sent email to me asking if there is a way to convert CollationID to Collation name. I replied asking more details about the requirement. Here is her reply.
Pinal,
I am in a trouble right now. Due to a hardware crash, I lost many of database files. Unfortunately, I don’t have backups, but I was able to retrieve MDF files. I was trying to follow your blog
How to Build Three Part Name from Object_ID? – Interview Question of the Week #134
Question:Â How to Build Three Part Name from Object_ID?
SQL SERVER – FIX: The Log for Database Cannot be Shrunk Until All Secondaries Have Moved Past the Point Where the Log was Added
While preparing for a demo for a client I was hit with an interesting error in AlwaysOn Availability Group backup and restore scenario. In my lab setup, I had four nodes SQLAUTH1 to SQLAUTH4 and I have always on high availability turned on SQL Server 2016. I played and did several operations with database and found that I have bloated the transaction log file to 100 GB. And now I need to shrink the transaction log on SQLAUTH1. As soon as I did that, I was welcomed with below message about database cannot be shrunk until all secondaries have moved past the point.
SQL SERVER – Caution: Adding Node in AlwaysOn Availability Group
It is interesting to see that in the past few days I have seen a similar pattern of an issue hit by three clients. All of them contacted me for a short engagement for the same issue. As you might know, every single day I keep two slots available for On Demand (50 minutes) so here is one of their emails. Let us learn about adding node in the AlwaysOn availability group.Â