Quick verdict
This choice is normally made for you by the database engine. If you run Oracle Database, especially in Oracle Cloud where it is included, use Oracle Data Safe for assessment, audit collection, discovery and masking. If you run Azure SQL or SQL Server, use Microsoft Defender for SQL for vulnerability scans and threat alerts, and keep SQL auditing for the evidence trail. Organisations with both engines usually run both services side by side and feed their alerts into one SIEM; the comparison below shows where the two differ so you can fill the gaps.
Oracle Data Safe is a regional Oracle Cloud Infrastructure service that connects to Oracle databases. Its documentation lists security assessment, user assessment, activity auditing, data discovery, data masking, data subsetting for non-production copies, alerts and management of SQL Firewall, which is built into Oracle AI Database 26ai. Targets include Autonomous AI Databases, OCI database systems, Exadata Cloud@Customer, on-premises Oracle databases, Oracle databases on compute instances in OCI or other clouds, and Amazon RDS for Oracle, connected over TLS or encrypted TCP through private endpoints or an on-premises connector.
Microsoft Defender for SQL is not a separate product but two plans inside the Defender for Databases plan of Microsoft Defender for Cloud. Defender for Azure SQL Databases protects Azure SQL single databases and elastic pools, Azure SQL Managed Instance and Synapse dedicated SQL pools; Defender for SQL Servers on Machines protects SQL Server 2012 to 2022 on Azure VMs and SQL Server enabled by Azure Arc, which is how on-premises, AWS and Google Cloud machines are covered. Each plan combines vulnerability assessment with Advanced Threat Protection alerts.
Side by side
| Aspect | Oracle Data Safe | Microsoft Defender for SQL |
|---|---|---|
| Engines covered | Oracle Database only | Azure SQL Database, SQL Managed Instance, Synapse dedicated SQL pools, SQL Server 2012 to 2022 |
| Where targets can run | OCI, Cloud@Customer, on premises, compute instances in other clouds, Amazon RDS for Oracle | Azure, plus on premises, AWS and Google Cloud through Azure Arc |
| Configuration assessment | Security assessment against STIG, CIS benchmarks, GDPR recommendations and Oracle practice | Vulnerability assessment scans with baselines and remediation steps |
| User and privilege review | User assessment of highly privileged and risky accounts | Permission findings within vulnerability assessment |
| Threat detection | Alerts from audit events and alert policies | Advanced Threat Protection: potential SQL injection, anomalous access and query patterns, brute force, suspicious activity |
| Audit trail | Collects and retains audit records: 12 months online plus up to 6 years archive | Not a full audit trail; use SQL Server Audit or Azure SQL auditing |
| Discovery and masking | Sensitive data discovery, masking and subsetting for non-production copies | Not part of the plan (Azure SQL has separate dynamic data masking) |
| Blocking | SQL Firewall allow lists (Oracle AI Database 26ai), managed centrally | No: alerts with mitigation guidance only |
| How it is enabled | Register each target database with the service | Enable per subscription; all supported resources, including new ones, are protected |
| Charging | Included with Oracle cloud databases; 1 million audit records per target per month free; on-premises targets billed (waived to 28 February 2027) | Azure consumption billing via Defender for Cloud after a 30-day trial; DWU model in preview |
Key differences
Scope: security toolkit versus threat detection plan
Data Safe is a broad toolkit for Oracle databases. Besides assessment and alerts it collects audit records centrally, manages audit policies, discovers sensitive columns, masks and subsets data for test copies, and manages SQL Firewall allow lists on Oracle AI Database 26ai. For an Oracle team it can replace several separate tools, although an on-premises network firewall or multi-engine monitoring still needs another product.
Defender for SQL is narrower by design. It tells you what is misconfigured (vulnerability assessment) and raises alerts when activity looks like an attack (Advanced Threat Protection), with links to Microsoft Sentinel for investigation. It does not keep an audit trail, does not mask data and does not block queries, so most Azure estates pair it with Azure SQL auditing or SQL Server Audit and with other controls for masking and access.
Reaching databases outside the home cloud
Both services reach beyond their own cloud, by different routes. Data Safe connects directly to Oracle databases on premises or on compute instances in any cloud through private endpoints or an on-premises connector, and it supports Amazon RDS for Oracle.
Defender for SQL covers SQL Server outside Azure through Azure Arc: the machine must be onboarded to Arc and registered as an Arc-enabled SQL Server, and the Defender for SQL extension then collects data through Extended Events from SQL Server 2017 onward and SQL Server audit logs on earlier versions, on Windows Server 2012 R2 or later. Microsoft notes the extension needs sysadmin rights for the SQL service account. AWS and Google Cloud accounts can also be connected to Defender for Cloud.
Audit retention and evidence
If an auditor asks for a year of database activity, Data Safe can answer from its own store: audit records are kept online for up to 12 months and can be archived for six more years, seven in total, and archived data can be retrieved up to six times per month per target. Paid audit collection beyond the free allowance is enabled by default and can be switched off per target, which stops collection until the next month.
Defender for SQL is not designed as evidence storage. For SQL Server and Azure SQL, the audit trail comes from SQL Server Audit or Azure SQL auditing, written to a destination you configure; Defender's alerts sit on top. Budget for that storage and retention separately when comparing costs.
Billing models
Data Safe is included at no additional cost with Oracle cloud databases; Oracle's Autonomous AI Database documentation says it is included for all workloads. Every target gets the first 1 million audit records collected per month free, with overage at Oracle Cloud price list rates. On-premises databases, databases on compute instances and Amazon RDS for Oracle are normally billed per registered target, but Oracle is waiving those charges from 12 June 2026 to 28 February 2027 (audit overage still applies).
Defender for SQL is billed through Microsoft Defender for Cloud, which is free for the first 30 days. Microsoft's FAQ says SQL Servers on Machines is billed per protected server, not per database. A preview billing model in the Defender portal replaces these plans with Defender Workload Units (DWUs) and one consolidated Defender for Databases plan, so cost models may change.
Pricing and licensing
Oracle Data Safe. Included with Oracle cloud databases at no additional cost; 1 million audit records per target per month free, with paid overage (on by default, switchable per target). On-premises, compute-instance and Amazon RDS for Oracle targets are normally billed per target, with charges waived from 12 June 2026 to 28 February 2027. Per-target and overage prices are on the oracle.com price list, which could not be read automatically, so they are not quoted. A 30-day free trial is available.
Microsoft Defender for SQL. Azure consumption billing through Defender for Cloud after a 30-day free trial; SQL Servers on Machines is billed per server, not per database. No price is quoted here: the public pricing page renders its figures only in the browser, and Microsoft's machine-readable price list shows several Defender for SQL meters (per instance-hour, per vCore-hour and per node-month) without stating which applies to which resource type. Use the Defender for Cloud pricing page or the Azure pricing calculator for your resources, and note the preview DWU model.
Pricing checked on the vendors' official pages on 7 November 2026. Prices change; confirm before buying.
Where each one leads
Oracle Data Safe strengths
- Assessment, user review, audit collection, discovery, masking and subsetting in one managed console
- No additional cost for Oracle cloud databases, apart from audit overage
- Long audit retention: 12 months online plus up to 6 years archive
- Manages SQL Firewall allow lists on Oracle AI Database 26ai
- Reaches on-premises, other-cloud and Amazon RDS for Oracle databases without host agents
Microsoft Defender for SQL strengths
- Enabled per subscription, automatically covering new resources
- Threat alerts for SQL injection, brute force and anomalous access with Sentinel investigation
- Covers Azure SQL, Managed Instance, Synapse and SQL Server 2012 to 2022
- Extends to on-premises, AWS and Google Cloud SQL Server through Azure Arc
- No appliances or separate consoles beyond Defender for Cloud
Limitations
Oracle Data Safe limitations
- Oracle Database only
- Per-target and overage prices sit on the Oracle price list, not in the documentation
- If paid audit usage is switched off, collection stops once the free monthly limit is reached
- SQL Firewall management applies to Oracle AI Database 26ai
Microsoft Defender for SQL limitations
- Microsoft SQL only within these plans
- No audit trail, masking or blocking; other tools are still needed
- Machines outside Azure must be onboarded to Azure Arc, with sysadmin rights for the extension
- Billing is moving to Defender Workload Units (preview) and meters are hard to map to resources
When to choose each
Choose Oracle Data Safe if
- Your databases are Oracle, in OCI or elsewhere
- You want audit records collected and retained by the service for compliance evidence
- You need discovery and masking before copying production data to test
- You are rolling out SQL Firewall on Oracle AI Database 26ai
Choose Microsoft Defender for SQL if
- Your databases are Azure SQL or SQL Server
- You want threat alerts and vulnerability scans with minimal setup across a subscription
- You already use Defender for Cloud and Microsoft Sentinel
- You want the same protection on on-premises SQL Server through Azure Arc
When neither is right
- You need one tool for many engines (Oracle, SQL Server, PostgreSQL and more): see IBM Guardium vs Imperva or DataSunrise.
- You need a network SQL firewall in front of on-premises Oracle databases: see DataSunrise vs Oracle Audit Vault.
- Your databases are on AWS RDS or Aurora: see AWS Database Activity Streams.
- You need SQL Server permission and configuration auditing outside Azure without Arc: see Idera SQL Secure.
Final recommendation
Pick by engine first: Oracle Data Safe for Oracle Database, Microsoft Defender for SQL for Azure SQL and SQL Server. Beyond that, know what each leaves out. Data Safe gives Oracle teams a wide managed toolkit, including audit retention and masking, but nothing for other engines. Defender for SQL gives Azure teams low-effort scanning and threat alerts, but you still need SQL auditing for evidence and other tools for masking and blocking. In a mixed estate, run both and send their alerts to the same SIEM.
Frequently asked questions
Can Oracle Data Safe protect SQL Server?
No. Data Safe connects to Oracle databases only: Autonomous AI Databases, OCI database systems, Cloud@Customer, on-premises Oracle databases, Oracle databases on compute instances and Amazon RDS for Oracle.
Can Defender for SQL protect Oracle?
No. Defender for SQL covers Azure SQL Database, SQL Managed Instance, Synapse dedicated SQL pools and SQL Server. Defender for Cloud has a separate plan for open-source relational databases; no Oracle Database plan was found on the pages checked.
Is Oracle Data Safe free?
For Oracle cloud databases it is included at no additional cost, and each target gets 1 million audit records per month free. On-premises and compute-instance targets are normally billed per target, with charges waived from 12 June 2026 to 28 February 2027, and audit overage is charged at price list rates.
Does Defender for SQL replace SQL Server auditing?
No. It raises threat alerts and runs vulnerability assessments, but it is not a full audit trail. Keep SQL Server Audit or Azure SQL auditing for compliance evidence.
Which one can block queries?
Data Safe manages SQL Firewall allow lists, which the Oracle AI Database 26ai kernel enforces. Defender for SQL does not block; it raises alerts with mitigation guidance.
Sources
- Oracle Data Safe overview
- Oracle Data Safe service limits
- Oracle Data Safe audit profiles (free records and paid usage)
- Oracle Data Safe promotion for on-premises databases
- Microsoft Learn: Defender for Azure SQL Databases overview
- Microsoft Learn: Enable Defender for SQL Servers on Machines
- Microsoft Learn: Defender for Databases FAQ
- Microsoft Learn: Defender Workload Units cost model (preview)
- Microsoft Defender for Cloud pricing
Checked November 2026.
How we research comparisons: our editorial method.