One evening I started receiving flood of alerts from almost every single Database server for one of my clients on SCOM console. The error message appeared as follow: “MSSQL 2016: SQL Server cannot authenticate using Kerberos because the Service Principal Name (SPN) is missing, misplaced, or duplicated.” Before I started technical investigation, first I wentContinue reading “SCOM Alert: MSSQL 2014: SQL Server cannot authenticate using Kerberos because the Service Principal Name (SPN) is missing, misplaced, or duplicated.”
Category Archives: MSSQL
SQL Server 2019 introduces recommendations for MAXDOP and Max memory during installation process.
Finally, two important SQL Server recommended settings have been introduced at the installation setup page. These are the settings that every DBA changes after every single installation. The settings are MaxDOP and Max Memory. MaxDOP: When an instance of SQL Server runs on a computer that has more than one CPU logical core, it detectsContinue reading “SQL Server 2019 introduces recommendations for MAXDOP and Max memory during installation process.”
SQL Server Bulk Insert failed (Access is Denied) on remote server, it’s delegation issue
Environment: Application server – where tableau/SharePoint application running, can’t give the ‘sa’ permission to the application domain\appuser. This domain\appuser is DBOwner of their DB Database Server – SQL Server 2016 Always on, services are running with domain\dbuser and has ‘sa’ permissions in SQL server File Share – A common share where the data is beingContinue reading “SQL Server Bulk Insert failed (Access is Denied) on remote server, it’s delegation issue”
Change collation at Instance level through rebuild databases in SQL Server 2017
Question: After SQL Server installation I realize that this SQL instance does not has the requirement of default collation. So how would I change it now either uninstall everything and install it again (of course not a smart move!) or rebuild system databases and change collation at Instance level? Answer: Easy and faster way toContinue reading “Change collation at Instance level through rebuild databases in SQL Server 2017”
Microsoft SQL Server roadmap
Here is the roadmap of Microsoft SQL Server:
Database deadlock issue, sometime an easy solution
Performance Tuning of database is always a challenge and becomes tricky sometime. Here is today’s topic deadlock which is a very common problem if you are dealing with databases Question: Sometime users complain they get an error message “their process was deadlocked with another process and was chosen as the victim.” After retry the entry, it worksContinue reading “Database deadlock issue, sometime an easy solution”
SQL Service account status with powershell
One of my client has the requirement to have SQL Service account running with domain account and should not be with local account. You may receive SSPI error after changing it to domain account. In order to fix that issue check my previous blog “How to register SPN for SQL service account“ Output:
Monitor basic Database parameters like Recovery Model, Page Verify, Auto Close, Auto Shrink, DB Owner, Auto Create Statistics Enabled, DB Create Date etc with PowerShell command.
iLearnSQL, 2020-06-16 Monitor basic Database parameters like Recovery Model, Page Verify, Auto Close, Auto Shrink, DB Owner, Auto Create Statistics Enabled, DB Create Date etc. with below script: Output:
How to register SPN or SSPI error:
To fix above error you need to register SPN. Verify if the SPN are already registered by command: setspn -l domain\xxxx; To register SPN, run below commands: setspn -A MSSQLSvc/abc.xx.companyname.com:1433 domain\xxxxx setspn -A MSSQLSvc/abc.xx.companyname.com domain\xxxxx setspn -A MSSQLSvc/abc:1433 domain\xxxxx setspn -A MSSQLSvc/ abc domain\xxxxx Make sure above SPN’s are registered, run below command: setspn -lContinue reading “How to register SPN or SSPI error:”
iLearnSQL 