2026-01-14
483 reads
SQL Server security
2026-01-07
585 reads
15 Practical Tips for Securing SQL Server
Securing SQL Server isn’t complicated, but it does require consistent attention to the areas where real risks arise, such as privileges, configuration, encryption, patching, and monitoring. This article outlines 15 practical, high-impact steps you can take to harden your SQL Server environment.
2025-12-17
Your Security Checkup
We often find security issues come from holes in the way we've set up systems. Steve asks if you perform security checkups on your systems.
2025-12-08
174 reads
2025-07-18
6,285 reads
2025-04-07
1,759 reads
A Few Best Practices for Strong SQL Server Security
Explore key strategies for securing SQL databases in this comprehensive guide. Learn about robust authentication, data encryption, SQL injection prevention, and more, with practical code examples. Enhance your database's security and performance by following tips from this article.
2024-03-01
7,062 reads
2024-02-05
463 reads
2024-02-02
392 reads
2024-01-22
339 reads
Blogs
Architecting Zero Downtime Deployments–Day of Data Boston
By Steve Jones
Here are the resources for my talk at Day of Data Boston. Slides –...
The Book of Redgate:A Prehistory
By Steve Jones
I’ve covered the values in a number of previous posts on the Book of...
Evidence-bound: what AgentDBA will and won’t link
By Arun Sirpal
When the evidence names the database, it says so. When it doesn’t, it stops....
Forums
Split Large Queries in Athena with a Simple Modulo Trick
Comments posted to this topic are about the item Split Large Queries in Athena...
Finding Trailing Spaces
Comments posted to this topic are about the item Finding Trailing Spaces
Question of the Day
Finding Trailing Spaces
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