In my earlier blog, we saw one possible cause database mail error due to SSL settings. Today we will learn about another Database Mail Error.
New Trends and Challenges in Database Administration
In the previous blog posts, we discussed the evolution of the DBA along with the challenges, changes and their upcoming trends. Data is the most critical part of any application. The changing nature of the data always brings new challenges to DBAs. New age DBAs now have to do many different tasks than before. Along with running the system at the most optimal settings, DBAs now have to get their hands dirty with development, DevOps, NoSQL technology as well as help organizations to migrate to the cloud.
SQL SERVER – gMSA: The Service Did Not Start Due to a Logon Failure
This is one of the most common errors which is seen my most DBA when they are using a domain account as the service account. In this blog, we would learn about the cause and solution of error The service did not start due to a logon failure while using gMSA.
SQL SERVER – Database Mail Error: The SMTP Server Requires a Secure Connection or the Client was not Authenticated. The Server Response Was: 5.5.1
Have you ever configured database mail using Gmail account? There are many articles on the internet describing the steps. In this blog, we would learn about fixing an error “The SMTP server requires a secure connection or the client was not authenticated” which you might see when database mail is used. Note that this can also appear for non-Gmail setups also. So, here we go.
SQL SERVER – Many BACKGROUND Threads with Command VDI_CLIENT_WORKER
There are so many wait types available in SQL Server and sometimes I feel that it’s an ocean of wait types. I have already written about most common wait types earlier. In this blog, we would learn about VDI_CLIENT_WORKER / VDI_CLIENT_OTHER wait type. SQL SERVER – Introduction to Wait Stats and Wait Types – Wait Type – Day 1 of 28
SQL SERVER – Event ID: 1135 – Cluster node ‘NodeName’ was Removed From the Active Failover Cluster Membership
When I work with customers, there are situations when I get chance to learn something from them. I was engaged with an AlwaysOn availability group engagement and got some interesting information from a customer which I am sharing here. In this blog, we would learn about how to solve event id 1135 – Cluster node ‘NodeName’ was removed from the active failover cluster membership.
SQL SERVER – Transfer Logins Error: Msg 15419: Supplied Parameter sid Should be Binary(16) – sp_help_revlogin
While I was writing my earlier blog, I came across another interesting issue with sp_help_revlogin script. In this blog we would learn about the cause of Msg 15419, “Supplied parameter sid should be binary(16)” while transferring the login using sp_help_revlogin and see how to fix it.