Discovery
Scans databases, schemas, tables, and columns using read-only `SELECT` access.
Ketch and Microsoft SQL Server
Find where personal data lives inside a SQL Server database, and fulfill deletion requests against it directly, managed through the same login and user lifecycle already in place for everything else.
About Microsoft SQL Server
SQL Server runs relational workloads across countless enterprise applications, often with schemas built up over years by different teams. Ketch's approach is to fit into existing SQL Server administration practices rather than requiring a separate, special-case process for privacy access.
Ketch connects to SQL Server through a Ketch Transponder with that fit in mind.
Capabilities
How Ketch works with Microsoft SQL Server
The Ketch SQL Server integration covers Discovery and Rights Orchestration for both Right to Access and Right to Delete.
Rights Orchestration
Requires `UPDATE` and `DELETE` access granted on top of that, scoped to the specific database, tables, and columns granted.
With Ketch, teams can
- Discover which SQL Server tables hold personal data using read-only access
- Grant rights-execution privileges separately from Discovery, deciding independently whether and when to authorize direct deletion and update
- Manage the Ketch login through standard SQL Server user lifecycle practices, rather than a special-case process
The gap
The problem this integration solves
An enterprise SQL Server instance built up over years of application development still needs personal data actually located and reachable:
01. Manually reviewing schemas across a long-lived database doesn't scale and misses changes made without a privacy review
02. A privacy integration managed outside standard SQL Server administration creates unnecessary process overhead
03. Fulfilling a deletion request against a database has historically meant a manually written query, slow and hard to prove complete
Ketch resolves this by fitting the connected login into normal SQL Server administration, and by separating discovery from execution as two distinct privilege grants.
Why Ketch
Why teams choose Ketch for Microsoft SQL Server privacy compliance
Permissioning infrastructure that governs Microsoft SQL Server the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.
Fits standard SQL Server administration
The Ketch login and user follow the organization's normal lifecycle practices rather than a special-case process.
Least-privilege by design
Discovery requires only `SELECT`; rights execution is a separate, explicit grant.
Backed by enforcement precedent
Regulators increasingly expect businesses to prove technical enforcement, not just describe it on paper, the same underlying expectation that applies to knowing what personal data a database holds.
Questions about the Microsoft SQL Server integration
Related reading
Expert insights for teams connecting Microsoft SQL Server
Integrations
Pre-built APIs with 1,000+ systems, apps, and models
Ketch ships connectors and SDKs so consent, rights, and policy flow into your CDPs, warehouses, ad platforms, and AI stack — without a custom data pipeline.
See Microsoft SQL Server permissioning running end to end
Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect Microsoft SQL Server yourself.
Get Started Free
Get started in less than 5 min