Check if the SPN is already registered:
setspn -l domain\xxxxx
If not, 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
Verify again,
setspn -l domain\xxxxx
setspn -A MSSQLSvc/abc.xx.companyname.com:1433 domainxxxxx setspn -A MSSQLSvc/abc.xx.companyname.com domainxxxxx setspn -A MSSQLSvc/abc:1433 domainxxxxx setspn -A MSSQLSvc/ abc domainxxxxx
As a part of my DBA activities, I do a lot of SQL Server installations every week. Most of the time, I install the instance with the default collation. A collation is a configuration setting in SQL Server that determines how the database engine should read the data. SQL Server has huge list of collations […]
2022-12-26 (first published: 2020-08-03)
17,739 reads
I bet, each DBA would change some settings after the SQL Server installation as per their company standard . I wrote this PowerShell script for one of my client who has below standards: Port should be 1433, static Disable SQL telemetry* & SQLWriter services Change recovery model to FUll for all databases except tempdb and […]
2020-07-02 (first published: 2020-06-21)
2,514 reads
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:
2020-06-17
953 reads
I have created this script for one of our client, the requirement was all the databases should be in full recovery model and should be monitored. Also, I added other important parameters like AutoShrink, AutoClose etc. Output:
2020-06-16
1,029 reads
2020-06-15
43 reads
