Guarding Against SQL Injection at the Database Layer (SQL Server)
This article presents a way to check and validate input before using it in your dynamic SQL queries to prevent SQL Injection problems.
2026-03-02
3,193 reads
This article presents a way to check and validate input before using it in your dynamic SQL queries to prevent SQL Injection problems.
2026-03-02
3,193 reads
Windows is changing its security, which will affect SQL Server.
2026-02-14
356 reads
This article is a follow-up to SQL Server DBaaS Vulnerability: Decrypting System Code & Exfiltrating User Data, in which we saw some vulnerabilities that affected pretty much all DBaaS offerings available in the cloud. Now, we’ll look at another vulnerability that once again affects every major cloud vendor.
2026-01-30
Learn how attackers can exploit SQL Server replication cleanup jobs to escalate privileges from db_owner to sysadmin
2026-01-16
2026-01-14
450 reads
2026-01-07
566 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
133 reads
2025-07-18
5,950 reads
2025-04-07
1,684 reads
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers