Even though my consulting is mostly around performance tuning, I can see many customers who want to start using the new capabilities of SQL Server for their existing application as they plan to do an upgrade of their infrastructure. In one of engagement with a bank, they wanted to explore more about SQL Auditing capability. Since they were new I got engaged with them in implementing compliance, which they must follow. In the recent past, I have written below blogs on SQL Audit.
SQL SERVER – Event ID 1045 – No Matching Network Interface Found for Resource ‘Cluster IP Address’ IP address ‘10.10.10.10’ (Return Code was ‘5035’)
One of my clients implemented AlwaysOn Multi-subnet listener. This is one of the message which I have heard from few other AlwaysOn availability group customers who are having multi-subnet deployment. This client reported that they are not able to bring listener online on one node, which was added newly. When they attempted to fail over AG resource in the cluster, we could see below messages reported in event logs. Let us see how we can fix errors related to no matching network.
How to Find SQL Server Memory Use by Database and Objects? – Interview Question of the Week #121
Question: How to Find SQL Server Memory Use by Database and Objects?
SQL SERVER – My Thoughts – Autogrow of File ‘SQLAuth_Log’ in Database ‘SQLAuth’ was Cancelled by User or Timed Out After 30020 Milliseconds
If you are seeing this error in the ERRORLOG on your production server then you must read this blog. I have collected some information about the message and its causes. Let us learn about Autogrow of file.
SQL SERVER – Maintenance Plan – Backup Files Not Getting Deleted
Sometimes it is important to read the documentation before assuming things based on the text. This blog is the result of one of my quick interaction with a client who had an issue with Maintenance Plan which they created for backup files.
SQL Azure Database – Msg 40197, Level 20 – The Service has Encountered an Error Processing Your Request. Please Try Again. Error Code 40549
While trying to help one of my clients, I was shown below error which was received using bulk insert command. The command was used to move data from Azure Blob Storage to SQL Azure Database. Let us see how to fix the error processing request.
SQL SERVER – Database Mirroring Login Attempt Failed With Error: ‘Connection Handshake Failed. There is No Compatible Encryption Algorithm. State 22
One of my client was trying to convert database mirroring to the AlwaysOn availability group. They had a mirroring configure where the principal server was going to become a primary replica. When they attempted to join the AG, it was failing with an error. The error messages we were getting in the wizard are not helpful. I went ahead and looked into SQL Server ERRORLOG and found below the messages