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
2,683 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
2,683 reads
Windows is changing its security, which will affect SQL Server.
2026-02-14
337 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
447 reads
2026-01-07
562 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
131 reads
2025-07-18
5,945 reads
2025-04-07
1,684 reads
By HeyMo0sh
Microsoft Fabric (not to be confused with the more general term “fabric” in DevOps)...
By James Serra
I’m honored to be hosting T-SQL Tuesday — edition #192. For those who may...
By Vinay Thakur
Continuing from Day 2 , we learned introduction on Generative AI and Agentic AI,...
I'm fairly certain I know the answer to this from digging into it yesterday,...
Hi Team, I am trying to refresh the Azure Synapse Dedicated pool from production...
hi everyone I am not sure how to write the query that will produce...
I have some data in a table:
CREATE TABLE #test_data
(
id INT PRIMARY KEY,
name VARCHAR(100),
birth_date DATE
);
-- Step 2: Insert rows
INSERT INTO #test_data
VALUES
(1, 'Olivia', '2025-01-05'),
(2, 'Emma', '2025-03-02'),
(3, 'Liam', '2025-11-15'),
(4, 'Noah', '2025-12-22');
If I run this query, how many rows are returned?
SELECT *
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t; See possible answers