Connecting SSMS to Azure storage failed with 400 Bad Request: authentication failed for account and the provided key. Here is the cause and the fix.
SQL SERVER – FCB::Open Failed – TEMPDB Files Fail to be Created with Error: “CREATE FILE Encountered Operating System Error 3”
SQL Server would not start: FCB::Open failed because TempDB files could not be created, with operating system error 3. Here is how I fixed it.
SQL SERVER – FIX: Msg 8180 – Statement(s) Could not be Prepared. Deferred Prepare Could not be Completed
A linked server query with OPENQUERY gave Msg 8180: Statement(s) could not be prepared. Deferred prepare could not be completed. Here is what I learned and the fix.
SQL SERVER – FIX: Msg 9514 – XML Data Type is Not Supported in Distributed Queries
Querying a table with an XML column over a linked server fails with Msg 9514: XML data type is not supported in distributed queries. Here is the fix.
SQL SERVER – FIX: Cannot Connect to SQL in Azure Virtual Machine From Laptop
SSMS on my laptop could not connect to SQL in Azure Virtual Machine, even though it worked fine on the VM itself. Here is how I fixed the connection.
SQL SERVER – Unable to Set Cloud Witness. Error: The Client and Server Cannot Communicate, Because They do Not Possess a Common Algorithm
Adding a cloud witness to my cluster failed: The client and server cannot communicate, because they do not possess a common algorithm. I share the fix that worked.
SQL SERVER – FIX: Msg 41105: Failed to Create the Windows Server Failover Clustering (WSFC) Resource With Name and Type ‘SQL Server Availability Group’
Creating an availability group failed with Msg 41105: Failed to create the WSFC resource with type ‘SQL Server Availability Group’. Here are ways to fix it.