This blog post will cover 11 tips for avoiding common SQL server mistakes. From indexing to security, these tips will help you optimize your database’s performance.
SQL SERVER – 5 Performance Optimizations Must Do for TempDB
We fixed quite a lots of things at customer place with regards to TempDB and he finally was able to get “the Flash” fast performance.
SQL SERVER – Docker Volume and Persistent Storage
I have received some rave reviews of my article on SQL SERVER – How to Get Started with Docker Containers with Latest SQL Server?. It was amazing to hear that people really get started after reading my article on docker. One of the most popular questions I keep on receiving was what happens when we have to patch or upgrade SQL Server. Well, that is a fantastic question. In today’s blog, I will explain to you how we can get Docker Volume and Persistent Storage.
Get-AzureStorageBlob: The Remote Server Returned an Error: (403) Forbidden. HTTP Status Code: 403 – HTTP Error Message: This Request is Not Authorized to Perform This Operation
I was working with one of my clients and they wanted to clean up old backup blobs from Azure. I have already blogged and shared my script. In this blog we would learn how to fix error: (403) Forbidden – This request is not authorized to perform this operation. SQL SERVER – PowerShell Script – Remove Old SQL Database Backup Files From Azure Storage
SSMS – Azure Storage Error – A Connection Attempt Failed Because the Connected Party did not Properly Respond After a Period of Time
This was an interesting situation where I learned something new. In this blog we would learn about error – “A connection attempt failed because the connected party did not properly respond after a period of time.” while using “Azure Storage” option in SQL Server Management Studio.
SQL SERVER – Unable to Set Cloud Witness. Error: The Client and Server Cannot Communicate, Because They do Not Possess a Common Algorithm
Recently, I was trying to simulate a client’s environment for which I need to have windows cluster with cloud witness. It didn’t go well, and I encountered an error message. In this blog, I will share the solution of error – “The client and server cannot communicate, because they do not possess a common algorithm” which I received while adding cloud witness. I was following below documentation: Deploy a Cloud Witness for a Failover Cluster
SQL SERVER – PowerShell Script – Remove Old SQL Database Backup Files From Azure Storage
Earlier back, I wrote blog to help my blog reader SQL SERVER – Powershell Script – Remove Old SQL Database Backup Files from Azure Storage