2026-06-03
339 reads
2026-06-03
339 reads
A dangerous privilege-escalation path exists in SQL Server when cross-database ownership chaining, system database defaults, and overly permissive permissions are combined.
2026-04-24
Every few years, someone asks a familiar question: do we really still need to disable the sa account in SQL Server? After all, it’s 2026. SQL Server has better encryption, better auditing, better defaults, and more security features than ever before. Surely this old guidance belongs in the past?
2026-03-20
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
5,066 reads
Windows is changing its security, which will affect SQL Server.
2026-02-14
660 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
491 reads
2026-01-07
592 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
By Steve Jones
semaphorism – n. a conversational hint that you have something personal to say on...
This week I was at PASS Data Community Summit in Seattle, and I attended...
By James Serra
(This is the third post in a three-part series on how AI is changing...
Comments posted to this topic are about the item Pay for Performance, which is...
WhatsApp:0817819444 Jl. Pemuda No.3 C, Tawangsari, Leteh, Kec. Rembang, Kabupaten Rembang, Jawa Tengah 59217
WhatsApp:0817819444 Jl. Pemuda No.57B, Blora, Tempelan, Kec. Blora, Kabupaten Blora, Jawa Tengah 58211
I have a table, dbo.bittest, where I am testing an application response. This has this structure:
CREATE TABLE [dbo].[BitTest] ( [insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()), [a] [bit] NULL ) ON [PRIMARY] GOMy application runs this code:
INSERT dbo.BitTest
(
insertdate,
a
)
VALUES
(DEFAULT, 'true')
GO
See possible answers