There are many rules in SQL Server setup which are checked to make sure that the user is not seeing failure at the end of the installation. Most of the rules are generally passed, but few of them are known to generate warnings. One of such rule is Microsoft .NET Application Security which can be seen below.
MySQL – Fix – Error – Your Password does not Satisfy the Current Policy Requirements
Just the other day I received an email from a MySQL user who has been struggling to set up his password due to the current policy requirements in MySQL. Let us see how we can identify what is his root cause and how to fix the issue with password security.Â
SQL SERVER – FIX: Msg 15170, Level 16, This login is the Owner of 1 Job(s). You Must Delete or Reassign these Jobs Before the Login can be Dropped
In our real life, there are lots of dependencies and same is true with SQL Server as well. This blog also talks about inability to drop a login due to a dependency.
Domain Controller – Startup Issue – Unable to Use Domain Account as Service Account When Read Only Domain Controller (RODC) is Involved
But now, as per company standards, they need to use a domain account as the service account. Let us learn more about that in this blog.
SQL SERVER – How to Enable Lock Pages in Memory?
Recently I received an email from user that he tried to search for solution on SQLAuthority.com for how to enable lock pages in memory but could not find a solution for it.
SQL SERVER – Msg 15137, Level 16 – Error Related to sp_xp_cmdshell_proxy_account
So far, I have written many blogs and I still feel that there are many errors and scenarios which are still uncovered. Whenever I see a new error and find a new solution, I always share it via this blog.  Let us see how we can fix errors related to sp_xp_cmdshell_proxy_account.
SQL SERVER – xp_logininfo – Msg 15404: Could not obtain information about Windows NT group/user, error code 0x2147
One of my client was running into the below error running xp_logininfo on some of their users. It was interesting that when they run the script to capture user information it works for the same user in another domain. They asked me if there is anything specific they can look for to find out the difference between the two users in the different domains?