SQL Server – What To Do When Disaster Strikes (5-Point Survival Guide)Chill, coffee first.When your SQL Server goes down, alarms are blaring, and managers are hovering, that sentence might...
2025-12-19 (first published: 2025-12-03)
712 reads
SQL Server Database Migration Pitfalls (and How to Fix Them)
Database migrations are where great product ideas go to die—unless you plan for SQL Server’s quirks and the realities of...
2025-11-21 (first published: 2025-11-05)
511 reads
Disable the sa login in SQL Server (and sleep better)If you run SQL Server in 2025 and your sa login is still usable, you’re giving attackers a giant, blinking...
2025-11-10 (first published: 2025-10-21)
2,141 reads
Why you should connect resiliently to SQL Server
Transient failures happen — in the cloud (Azure SQL) and on-prem. A resilient connection strategy lets your app recover gracefully instead of...
2025-11-05 (first published: 2025-10-13)
456 reads
Truncate Table Pitfalls
Truncating a table can be gloriously fast—and spectacularly dangerous when used carelessly. If you want the speed without the face-palm moments, here’s a practical, interview-ready guide to...
2025-10-29 (first published: 2025-10-08)
952 reads
Unused Indexes in SQL Server: Find them, vet them, and drop them safely
Indexes are fantastic when you’re reading data—and a tax when you’re writing it. Every INSERT/UPDATE/DELETE has to...
2025-10-28
988 reads
DBAs should never run SSMS under their everyday Windows account
If you open SSMS under the same Windows identity you use for email, browsing, and chat, you bring all that...
2025-10-22 (first published: 2025-10-07)
1,647 reads
Why Developers Shouldn’t Have sysadmin access in SQL Server
7 reasons—and exactly what to do instead
It can feel “faster” to hand developers sysadmin. In reality, it’s like giving them the master...
2025-10-06
559 reads
SELECT * feels convenient, but in SQL Server it bloats I/O, burns network bandwidth, blocks covering-index usage, and makes code brittle when schemas change. Specify only the columns you...
2025-10-02
77 reads
SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been...
2019-03-18 (first published: 2019-03-05)
17,213 reads
By Steve Jones
I caught this interesting item over on Pinal Dave’s blog: Eleven Interview Questions that...
By Hemantgiri
I use color-coded connections in SSMS to distinguish Production, Pre-Production, UAT, and Development. But...
WhatsApp CS 628218520154 Jl. Suryopranoto No.40, RT.12/RW.7, Petojo Utara, Kecamatan Gambir, Kota Jakarta Pusat,...
WhatsApp CS 628218520154 Jl. Pegangsaan Timur No.1, Cikini, Kec. Menteng, Kota Jakarta Pusat, Daerah...
WhatsApp CS 628218520154 Jl. Pintu Air Raya No.36 Q, RT.6/RW.1, Ps. Baru, Kecamatan Sawah...
I have some data in a SQL Server 2025 database. It looks like this for the dbo.Customer table:
CustomerID CustomerName PreferredName 1 Steve Steve 2 Andy Andy 3 Brian Brian 4 Allan Allan 5 Devin Devin 6 Steve Steve 7 Sally SallyI want to detect which names have a single trailing space. The CustomerName is a varchar() and the PreferredName is a CHAR(). Does this query detect the problem rows?
SELECT
CustomerID,
CustomerName,
PreferredName
FROM Customer
WHERE CustomerName <> RTRIM(CustomerName)
OR PreferredName <> RTRIM(PreferredName); See possible answers