Articles

Technical Article

It’s 2026. Why are databases still failing GDPR compliance audits?

This article examines three recurring database-layer failures documented in the EDPB’s 2026 enforcement findings: the complexity of executing erasure across relational schemas, the backup paradox that can silently undo compliant deletions, and the audit log contradiction that traps organizations between two competing obligations.

You rated this post out of 5. Change rating

2026-07-13

Blogs

Lean Six Sigma – Brief

By

When you have a project or system, it has to be optimized, tuned, and...

T-SQL Tuesday #200: Bad Query signals

By

NO AI was used to generate this content. Grammarly was used to check and...

Project Management – Part 1

By

The soul of project management is Process Group(PG) and Knowledge Area(KA). they are related...

Read the latest Blogs

Forums

Reading Parquet using openrowset

By saum70

Hi, We are looking out to read parquet file directly from on premise shared...

Impact of Single-Threaded PVS Cleanup on ADR in SQL Server 2019

By abdalah.mehdoini

We want to enable ADR on our SQL Server 2019 instances. I’ve heard that...

Forward Deployed Engineers

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Forward Deployed Engineers

Visit the forum

Question of the Day

DBCC CHECKDB Limits II

I have a SQL Server 2025 database that I want to check for corruption every night. One of the things we do is disable indexes used for ETL loads during the weekend and re-enable them on Monday morning. If we run DBCC over the weekend, are our disabled indexes checked for consistency?

See possible answers