SQL Server Privilege Escalation via Replication Jobs
Learn how attackers can exploit SQL Server replication cleanup jobs to escalate privileges from db_owner to sysadmin
2026-01-16
Learn how attackers can exploit SQL Server replication cleanup jobs to escalate privileges from db_owner to sysadmin
2026-01-16
2026-01-14
375 reads
2026-01-07
533 reads
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
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
122 reads
2025-07-18
5,889 reads
2025-04-07
1,682 reads
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
6,196 reads
2024-02-05
417 reads
2024-02-02
374 reads
By Ed Elliott
Running tSQLt unit tests is great from Visual Studio but my development workflow...
By James Serra
I remember a meeting where a client’s CEO leaned in and asked me, “So,...
By Brian Kelley
If you want to learn better, pause more in your learning to intentionally review.
Comments posted to this topic are about the item The Long Name
Comments posted to this topic are about the item Eight Minutes
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
I run this code to create a table:
When I check the length, I get these results:
A table name is limited to 128 characters. How does this work?