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)
24,224 reads
I was working on one of my clients server recently. This was during a normal maintenance monthly activity to reboot the database server every first weekend. I rebooted the machine, and as per the defined steps, I checked the SQL services after the reboot to ensure they were up. I verified all SQL Services and […]
2020-10-05
4,606 reads
Recently I was installing SQL Server 2017 and I could not believe a simple installation took up my whole day. I was installing an instance on one newly built Windows 2012 R2 server. After clicking next a few times, I got an error: a rule failure, for KB2919355. I downloaded the KB2919355 as mentioned in […]
2020-09-14
8,387 reads
Learn how to correct an error that is overloading SCOM by fixing an SPN.
2020-09-10
8,174 reads
Finally, two important SQL Server recommended settings have been introduced during the installation process. These are the settings that every DBA (should) change after every single installation. The settings are MaxDOP and Max Memory. This article looks at each of these settings and how they are presented during installation. MaxDOP When an instance of SQL […]
2020-09-01
10,361 reads
A failed SQL Server Service Pack upgrade is fixed with a trace flag.
2020-07-27
5,776 reads
2020-07-16
5,737 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,708 reads
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
2020-06-17 (first published: 2020-06-15)
8,060 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
1,121 reads
By Brian Kelley
My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...
By Steve Jones
“On the way to a grand goal, celebrate the smallest victories as if each...
Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...
QW49+7V2, Jl. RTA Milono, Menteng, Kec. Jekan Raya, Kota Palangka Raya, Kalimantan Tengah 74874
Jl. Alternatif Cibubur RT.005/09. Kel. Harjamukti, Cibubur, Kec. Cimanggis, Kota Depok, Jawa Barat 16454
Jl. Pakunegara No.32, Raja, Kec. Arut Sel., Kabupaten Kotawaringin Barat, Kalimantan Tengah 74112
How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?
See possible answers