{"id":46282,"date":"2026-08-10T15:47:55","date_gmt":"2026-08-10T13:47:55","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=46282"},"modified":"2026-08-10T15:47:58","modified_gmt":"2026-08-10T13:47:58","slug":"sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/","title":{"rendered":"SQL Server vs MongoDB: When the cloud is your adversary (Always Encrypted vs Queryable Encryption)"},"content":{"rendered":"\n

The real barrier to the cloud<\/h2>\n\n\n\n

When a company still refuses to put its sensitive data in the cloud, the reason usually isn’t cost or performance: it’s data sovereignty<\/strong>. In the cloud, someone else is the administrator of the machine; therefore the provider can, in theory, read the data files, see the data being used in memory, or read the backups. The threat model is no longer the external attacker but the privileged insider hosting the database.<\/p>\n\n\n\n

As covered previously on my blog Beyond TDE and TLS: Bridging the Data Security Governance Gap in Lower Environments<\/a><\/em>, various encryption methods can protect you. For example, TLS protects data in transit<\/em> and TDE protects it at rest<\/em>, but as soon as the engine runs a query, it handles plaintext in memory. So there are three states to protect: at-rest<\/em>, in-transit<\/em>, in-use<\/em>. The gap this article focuses on is the last one.<\/p>\n\n\n\n

That is exactly what Always Encrypted<\/a> (SQL Server) and Queryable Encryption<\/a> (MongoDB) target. The common principle: encryption and decryption happen client-side, in the driver; the keys never reach the engine. The data stays encrypted at rest, in transit, and<\/strong> during processing. The DBA, the cloud operator, the hypervisor admin: all of them see only cyphertext.<\/p>\n\n\n\n

That leaves one question: if the engine sees only cyphertext, how does it answer a WHERE<\/code> condition? Both database engines do answer it, but through different technical means.<\/p>\n\n\n\n

SQL Server: queryability lives in the cyphertext<\/h2>\n\n\n\n

To demonstrate all this, let’s start by creating a table with two columns, Salary and Department, encrypted deterministically on one side and randomized on the other:<\/p>\n\n\n

\nDROP TABLE IF EXISTS dbo.Employees;\nCREATE TABLE dbo.Employees (\n  Id         INT IDENTITY(1,1) PRIMARY KEY,\n  LastName   NVARCHAR(50) COLLATE Latin1_General_BIN2 NOT NULL,\n  FirstName  NVARCHAR(50) COLLATE Latin1_General_BIN2 NOT NULL,\n  DeptDet    NVARCHAR(30) COLLATE Latin1_General_BIN2 NOT NULL, -- will be DETERMINISTIC\n  DeptRand   NVARCHAR(30) COLLATE Latin1_General_BIN2 NOT NULL, -- will be RANDOMIZED\n  SalaryDet  INT NOT NULL, -- will be DETERMINISTIC\n  SalaryRand INT NOT NULL  -- will be RANDOMIZED\n);\nGO\n\nINSERT INTO dbo.Employees (LastName, FirstName, DeptDet, DeptRand, SalaryDet, SalaryRand) VALUES\n('Martin',  'Alice', 'Sales', 'Sales', 55000, 55000),\n('Dubois',  'Bob',   'Sales', 'Sales', 48000, 48000),\n('Bernard', 'Chloe', 'Sales', 'Sales', 52000, 52000),\n('Petit',   'David', 'IT',    'IT',    72000, 72000),\n('Durand',  'Emma',  'IT',    'IT',    68000, 68000);\n\n<\/pre><\/div>\n\n\n
Five rows: three Sales<\/code>, two IT<\/code>. The BIN2<\/code> collation is required by Always Encrypted (link to documentation<\/a>), and the master key lives outside the database (Key Vault, certificate store, or HSM).<\/p>\n\n\n\n
Column encryption isn’t done in T-SQL, because the engine doesn’t have the keys. It’s driven from the client (here in PowerShell), declaring for each value a deterministic column and its randomized twin:<\/p>\n\n\n
\nImport-Module SqlServer -MinimumVersion 22.0.59\n$sqlConnectionString = "Data Source=.\\LAB2025;Initial Catalog=AEDEMO;Integrated Security=True;Encrypt=False;Trust Server Certificate=False"\n$smoDatabase = Get-SqlDatabase -ConnectionString $sqlConnectionString\n\n$encryptionChanges  = @()\n$encryptionChanges += New-SqlColumnEncryptionSettings -ColumnName dbo.Employees.DeptDet    -EncryptionType Deterministic -EncryptionKey "CEK1"\n$encryptionChanges += New-SqlColumnEncryptionSettings -ColumnName dbo.Employees.DeptRand   -EncryptionType Randomized    -EncryptionKey "CEK1"\n$encryptionChanges += New-SqlColumnEncryptionSettings -ColumnName dbo.Employees.SalaryDet  -EncryptionType Deterministic -EncryptionKey "CEK1"\n$encryptionChanges += New-SqlColumnEncryptionSettings -ColumnName dbo.Employees.SalaryRand -EncryptionType Randomized    -EncryptionKey "CEK1"\n\nSet-SqlColumnEncryption -ColumnEncryptionSettings $encryptionChanges -InputObject $smoDatabase\n\n<\/pre><\/div>\n\n\n
In this example, I’m working on my 2025 SQL Server instance, on the AEDEMO database, using the column encryption key CEK1<\/code> I created beforehand (itself protected by a column master key stored outside the database).<\/p>\n\n\n\n
We check that the engine sees the right type per column:<\/p>\n\n\n
\nSELECT c.name, c.encryption_type_desc\nFROM sys.columns c\nWHERE c.object_id = OBJECT_ID('dbo.Employees');\n\n<\/pre><\/div>\n\n\n
\"\"<\/figure>\n\n\n\n
The deterministic mechanism works like this: same plaintext, same cyphertext<\/strong> (an injective function). On an Always Encrypted-enabled connection with Parameterization for Always Encrypted<\/em> and parameters for the predicates (never literals), equality works:<\/p>\n\n\n
\nDECLARE @d NVARCHAR(30) = 'Sales';\nSELECT DeptDet AS Enc, COUNT(*) FROM dbo.Employees WHERE DeptDet = @d\nGROUP BY DeptDet;\n\n<\/pre><\/div>\n\n\n
\"\"<\/figure>\n\n\n\n
The driver encrypts @d<\/code> with the same key, the server finds the encrypted values that are identical to the parameter, and the result is correct.<\/p>\n\n\n\n
You pay for it in three ways…<\/p>\n\n\n\n
First weakness: deterministic encryption can cause a data leak.<\/strong> You don’t need the keys to see it. Just connect without<\/em> Always Encrypted and read the table: the encrypted columns come out as raw binary.<\/p>\n\n\n
\nSELECT FirstName, DeptDet, DeptRand FROM dbo.Employees;\n\n<\/pre><\/div>\n\n\n
\"\"<\/figure>\n\n\n\n
Look at the DeptDet<\/code> column: Alice, Bob, and Chloe share exactly the same blob<\/strong>, and David and Emma share another. Two distinct values across five rows. The adversary doesn’t know what 0x012536\u2026<\/code> means, but reads the structure: two departments, one with three people, the other with two, and who goes with whom. The DeptRand<\/code> column, on the other hand, shows five all-different blobs: nothing to read.<\/p>\n\n\n\n
It’s harmless on five rows; it isn’t on a real table. On a low-cardinality column (region, sex, status), the distribution of blobs can be compared to a known distribution, and frequency analysis often reconstructs the plaintext. Microsoft’s documentation<\/a> puts it bluntly: an unauthorized user can guess information by examining patterns, especially when the set of possible values is small.<\/p>\n\n\n\n
Second weakness: randomized encryption blocks every query.<\/strong> With randomized encryption, the driver adds a fresh random value to each cell before encrypting, so the same input produces a different cyphertext every time. Therefore, the leak is gone but so is the query<\/span>:<\/p>\n\n\n
\nDECLARE @d NVARCHAR(30) = 'Sales';\nSELECT DeptRand AS Enc, COUNT(*) FROM dbo.Employees WHERE DeptRand = @d\nGROUP BY DeptRand;  \n\n<\/pre><\/div>\n\n\n
Msg 33277, Level 16, State 2, Line 6
Encryption scheme mismatch for columns\/variables ‘DeptRand’, ‘@d’. The
encryption scheme for the columns\/variables is (encryption_type =
‘RANDOMIZED’, \u2026) and the expression near line ‘6’ expects it to be
DETERMINISTIC, or RANDOMIZED, a BIN2 collation for string data types,
and an enclave-enabled column encryption key, or PLAINTEXT.<\/em><\/p>\n\n\n\n
The server can no longer compare, since the same plaintext produces a different cyphertext on every row. We gained confidentiality and lost the query. It’s all or nothing.<\/p>\n\n\n\n
Third weakness: no range, even with deterministic.<\/strong> Byte equality says nothing about order:<\/p>\n\n\n
\nDECLARE @s INT = 55000;\nSELECT FirstName FROM dbo.Employees WHERE SalaryDet &lt; @s;\n\n<\/pre><\/div>\n\n\n
WHERE SalaryDet < @s<\/code> fails even though the column is deterministic. Sorting, BETWEEN<\/code>, LIKE<\/code>: out of reach for Always Encrypted alone.<\/p>\n\n\n\n
The verdict is clear: bare Always Encrypted means equality, or nothing (=, IN, GROUP BY, and DISTINCT supported).<\/p>\n\n\n\n
MongoDB: queryability lives in a protocol<\/h2>\n\n\n\n
MongoDB’s Queryable Encryption makes optimal use of randomized encryption. On the server side, everything is Randomized-encrypted, as the documentation explains<\/a>: the server has no knowledge of the data it processes<\/em>. The encrypted view<\/strong> (a client connected without the keys) confirms it: even the three Sales<\/code> employees come out with all-different BinData<\/code>.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
No frequency leak, unlike SQL Server’s deterministic encryption. With the keys, the same find<\/code> returns the plaintext:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
The technical mechanism behind this lies in the collection’s declaration. Each encrypted field carries a queryType<\/code>, its parameters, and a distinct key (keyId<\/code>), one Data Encryption Key per field, which is mandatory:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
And queries with equality tests, range, and even equality on a field declared as range all work:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
On the server side, MongoDB then maintains encrypted index structures, and for each query the driver generates cryptographic tokens<\/em> that the server checks against those structures without ever seeing the plaintext. This is a searchable encryption<\/a><\/em> scheme. Range is available in GA<\/strong>, with no special hardware.<\/p>\n\n\n\n
The real difference comes down to one thing: the driver<\/h2>\n\n\n\n
On the SQL Server side, the driver’s work stays thin: it encrypts the parameters, rewrites the query, decrypts the results. Queryability itself is already carried by the cyphertext; the driver doesn’t have to handle it. On the MongoDB side, the driver carries the whole protocol: it generates the tokens checked against the encrypted indexes.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Once the collection is in place, find({ department: \"Sales\" })<\/code> is written like a normal query and the driver handles the encryption on its own. Each encrypted field needs its own key (Data Encryption Key). The master key must be pinned, otherwise orphaned keys return an HMAC validation failure<\/code> error. And the encryption API is only available from a client created as encrypted, so not from a standard Compass connection, for example.<\/p>\n\n\n\n
Summary<\/h2>\n\n\n\n
<\/th>Always Encrypted<\/th>Queryable Encryption<\/th><\/tr><\/thead>
Server-side encryption<\/td>deterministic or<\/em> randomized<\/td>always randomized<\/td><\/tr>
Equality<\/td>yes (deterministic)<\/td>yes<\/td><\/tr>
Range \/ sort<\/td>no<\/td>yes (GA)<\/td><\/tr>
Frequency analysis attack<\/td>yes, with deterministic<\/td>no<\/td><\/tr>
Where the search happens<\/td>in the cyphertext<\/td>in the protocol<\/td><\/tr>
Driver weight<\/td>light<\/td>heavy<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
What if you wanted range while staying on SQL Server?<\/h2>\n\n\n\n
This is where secure enclaves<\/a><\/strong> come in. The engine delegates the computation to an enclave: a protected memory region where the data is decrypted and processed in the clear, out of reach, including from the machine’s administrator. This is what unlocks range, LIKE<\/code>, sorting, and in-place encryption: inside the enclave the server no longer compares encrypted bytes, it works on the plaintext. This gain has a price. It requires compatible hardware or secure virtualization, an attestation service to deploy and maintain, and keys configured for the enclave, which noticeably increases architectural complexity compared with classic Always Encrypted.<\/p>\n\n\n\n
But it also changes the nature of the trust<\/strong>. Queryable Encryption rests on a cryptographic guarantee: the server cannot<\/em> read, it’s a mathematical property. Enclaves rest on a hardware guarantee: you trust the CPU, and its attestation, to isolate the protected region.<\/p>\n\n\n\n
There remains a third path, often mentioned: homomorphic encryption (FHE), which computes directly on the cyphertext without ever decrypting it. Elegant on paper, but out of the game for database search: the computational cost is massive and response time collapses as the volume grows. So the practical choice really does play out between the two worlds described here.<\/p>\n","protected":false},"excerpt":{"rendered":"
When the cloud admin is the threat: how SQL Server and MongoDB let you query encrypted data, and what each approach costs.<\/p>\n","protected":false},"author":157,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":"","_members_access_role":[],"_members_access_error":""},"categories":[955,229,3788,1739,99],"tags":[135,677,51],"type_dbi":[],"class_list":["post-46282","post","type-post","status-publish","format-standard","hentry","category-cloud","category-database-administration-monitoring","category-mongodb","category-nosql","category-sql-server","tag-cloud","tag-nosql-mongodb","tag-sql-server"],"acf":[],"yoast_head":"\nSQL Server vs MongoDB: When the cloud is your adversary (Always Encrypted vs Queryable Encryption) - dbi Blog<\/title>\n<meta name=\"description\" content=\"When the cloud admin is the threat: how SQL Server and MongoDB let you query encrypted data, and what each approach costs.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SQL Server vs MongoDB: When the cloud is your adversary (Always Encrypted vs Queryable Encryption)\" \/>\n<meta property=\"og:description\" content=\"When the cloud admin is the threat: how SQL Server and MongoDB let you query encrypted data, and what each approach costs.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-10T13:47:55+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-10T13:47:58+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/08\/image-32.png\" \/>\n\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t<meta property=\"og:image:height\" content=\"251\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Louis Tochon\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Louis Tochon\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\\\/\"},\"author\":{\"name\":\"Louis Tochon\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/e4195b0cb120295b3407a502c23e75b6\"},\"headline\":\"SQL Server vs MongoDB: When the cloud is your adversary (Always Encrypted vs Queryable Encryption)\",\"datePublished\":\"2026-08-10T13:47:55+00:00\",\"dateModified\":\"2026-08-10T13:47:58+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\\\/\"},\"wordCount\":1326,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2026\\\/08\\\/image-32.png\",\"keywords\":[\"Cloud\",\"NoSQL MongoDB\",\"SQL Server\"],\"articleSection\":[\"Cloud\",\"Database Administration & Monitoring\",\"MongoDB\",\"NoSQL\",\"SQL Server\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\\\/\",\"name\":\"SQL Server vs MongoDB: When the cloud is your adversary (Always Encrypted vs Queryable Encryption) - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2026\\\/08\\\/image-32.png\",\"datePublished\":\"2026-08-10T13:47:55+00:00\",\"dateModified\":\"2026-08-10T13:47:58+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/e4195b0cb120295b3407a502c23e75b6\"},\"description\":\"When the cloud admin is the threat: how SQL Server and MongoDB let you query encrypted data, and what each approach costs.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2026\\\/08\\\/image-32.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2026\\\/08\\\/image-32.png\",\"width\":350,\"height\":251},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SQL Server vs MongoDB: When the cloud is your adversary (Always Encrypted vs Queryable Encryption)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/e4195b0cb120295b3407a502c23e75b6\",\"name\":\"Louis Tochon\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ce0ee48c64e763e6c4076e21c80729d15bc4493288aeb8695125c69082100e10?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ce0ee48c64e763e6c4076e21c80729d15bc4493288aeb8695125c69082100e10?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ce0ee48c64e763e6c4076e21c80729d15bc4493288aeb8695125c69082100e10?s=96&d=mm&r=g\",\"caption\":\"Louis Tochon\"},\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/louistochon\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"SQL Server vs MongoDB: When the cloud is your adversary (Always Encrypted vs Queryable Encryption) - dbi Blog","description":"When the cloud admin is the threat: how SQL Server and MongoDB let you query encrypted data, and what each approach costs.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/","og_locale":"en_US","og_type":"article","og_title":"SQL Server vs MongoDB: When the cloud is your adversary (Always Encrypted vs Queryable Encryption)","og_description":"When the cloud admin is the threat: how SQL Server and MongoDB let you query encrypted data, and what each approach costs.","og_url":"https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/","og_site_name":"dbi Blog","article_published_time":"2026-08-10T13:47:55+00:00","article_modified_time":"2026-08-10T13:47:58+00:00","og_image":[{"width":350,"height":251,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/08\/image-32.png","type":"image\/png"}],"author":"Louis Tochon","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Louis Tochon","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/"},"author":{"name":"Louis Tochon","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/e4195b0cb120295b3407a502c23e75b6"},"headline":"SQL Server vs MongoDB: When the cloud is your adversary (Always Encrypted vs Queryable Encryption)","datePublished":"2026-08-10T13:47:55+00:00","dateModified":"2026-08-10T13:47:58+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/"},"wordCount":1326,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/08\/image-32.png","keywords":["Cloud","NoSQL MongoDB","SQL Server"],"articleSection":["Cloud","Database Administration & Monitoring","MongoDB","NoSQL","SQL Server"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/","url":"https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/","name":"SQL Server vs MongoDB: When the cloud is your adversary (Always Encrypted vs Queryable Encryption) - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/08\/image-32.png","datePublished":"2026-08-10T13:47:55+00:00","dateModified":"2026-08-10T13:47:58+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/e4195b0cb120295b3407a502c23e75b6"},"description":"When the cloud admin is the threat: how SQL Server and MongoDB let you query encrypted data, and what each approach costs.","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/08\/image-32.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/08\/image-32.png","width":350,"height":251},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-vs-mongodb-when-the-cloud-is-your-adversary-always-encrypted-vs-queryable-encryption\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"SQL Server vs MongoDB: When the cloud is your adversary (Always Encrypted vs Queryable Encryption)"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/e4195b0cb120295b3407a502c23e75b6","name":"Louis Tochon","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/ce0ee48c64e763e6c4076e21c80729d15bc4493288aeb8695125c69082100e10?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/ce0ee48c64e763e6c4076e21c80729d15bc4493288aeb8695125c69082100e10?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/ce0ee48c64e763e6c4076e21c80729d15bc4493288aeb8695125c69082100e10?s=96&d=mm&r=g","caption":"Louis Tochon"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/louistochon\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/46282","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/157"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=46282"}],"version-history":[{"count":34,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/46282\/revisions"}],"predecessor-version":[{"id":46373,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/46282\/revisions\/46373"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=46282"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=46282"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=46282"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=46282"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}