| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Data warehouses | Data platform | 0% | 5 of 26 | 12% | 41 | accepted challenger | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Data virtualization | Data platform | 0% | 34 of 99 | 0% | 1 | under 10 labels · led by Denodo at 28% |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| Data warehouses | 0% | 0% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 8 → 5 of 26 |
| Data virtualization | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 34 of 99, unchanged |
Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.
The floor is 11 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 1 | 2 | 0 | 3 |
| GPT-5.4 mini | 0 | 1 | 2 | 0 | 3 |
| Gemini 3.5 Flash | 0 | 0 | 1 | 0 | 1 |
| Perplexity Sonar | 0 | 1 | 0 | 0 | 1 |
| Grok 4.20 | 0 | 2 | 1 | 1 | 4 |
| Mistral Small | 0 | 0 | 1 | 1 | 2 |
| DeepSeek V4 Flash | 1 | 3 | 0 | 2 | 6 |
| Llama 4 Maverick | 0 | 0 | 5 | 0 | 5 |
| Qwen 3.7 Flash | 0 | 1 | 2 | 0 | 3 |
| Kimi K2 | 0 | 1 | 2 | 1 | 4 |
| GLM 4.7 FlashX | 0 | 2 | 0 | 0 | 2 |
| MiniMax M2.5 | 0 | 1 | 1 | 0 | 2 |
| GPT-6 Luna | 0 | 2 | 1 | 0 | 3 |
| Muse Glimmer 30B | 0 | 2 | 1 | 0 | 3 |
Verbatim evidence the judge attached to positive labels.
“If you want the safest picks, look toward open-table-format ecosystems ... or Databricks' lakehouse for its openness” DeepSeek V4 Flash · Data warehouses · negative prompt · first choice
“Your main need is a broader lakehouse platform for data engineering, machine learning, or AI—not just a conventional SQL warehouse.” GPT-6 Luna · Data warehouses · direct prompt · alternative
“Databricks if your needs go beyond warehousing into lakehouse, engineering, ML, and AI” GPT-5.4 mini · Data warehouses · paraphrase prompt · alternative
“Databricks — if you need heavy machine learning/AI workloads alongside analytics” DeepSeek V4 Flash · Data warehouses · scale prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“The DBU-based pricing can become unpredictable and expensive for small teams.” DeepSeek V4 Flash · Data warehouses · budget prompt · hard negative
“can lead to vendor lock-in due to its tight integration with cloud ecosystems and proprietary formats” Mistral Small · Data warehouses · negative prompt · soft negative
“higher costs/complexity for pure SQL/BI vs. warehouses. Pricing opacity for mixed workloads.” Grok 4.20 · Data warehouses · negative prompt · soft negative
“Cost overruns and complexity — likely overkill for most mid-market B2B companies.” DeepSeek V4 Flash · Data warehouses · direct prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 103 of the 125 answers that named Databricks SQL and are not a share of its labels.
355 of the 355 domain citations in answers naming Databricks SQL came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What Databricks SQL's own pages state, read September 28, 2026: kb.databricks.com/en_US/dbsql/update-the-databricks-sql-warehouse-owner, kb.databricks.com/en_US/dbsql/find-long-running-queries-in-your-sql-warehouse, kb.databricks.com/en_US/dbsql/sql-warehouse-spins-up-despite-no-queries-executed, kb.databricks.com/en_US/dbsql/cannot-customize-apache-spark-config-in-databricks-sql-warehouse, docs.databricks.com/aws/en/sql/dbsql-api-latest. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Databricks SQL's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Databricks SQL, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Databricks SQL by email, built from the raw record of the edition. It shows: