74 sources from practitioners, by month and sentiment.
Teams praise answer quality once a data team curates context, and every account that explains a good answer credits that curation. Their most frequent concerns are cost since usage billing began and deploying Genie Agents outside the UI. Most keep their BI tool beside Genie.
Positive, mixed and negative sources
21146
The score counts them as 20 positive, 13 mixed and 6 negative votes, one per author. See How the numbers work.
Their Genie Agent prototype over a client's transcribed call data, even without example questions or instructions, already beats the client's previous method of uploading transcripts to an LLM one by one.
Published Jul 22, 2026self-described: Client analyzing call transcripts in a Genie Agent
Positive
angryapathetic, Reddit commenter in r/databricks, consultant
The commenter deployed Genie for a client who likes it. They trust it more because it writes SQL against the data, where a plain model would guess the answer, and better instructions give better answers.
Published Dec 6, 2025self-described: Deployed Genie for a client
Positive
Whack_a_mallard, Reddit commenter in r/databricks, consultant
Having implemented Genie with multiple clients, both heavy and new Databricks users, the commenter reports positive results and sees it as a supplement to existing solutions.
Published Aug 5, 2025self-described: Implemented Genie with multiple clients
Positive
No_Presentation1421, Reddit commenter in r/databricks, consultant
The commenter calls Genie 95% curation. On a well-built layer of metric views, users are hard to pull back to dashboards, though instructions and context drift are hard to manage.
Published Jun 17, 2026self-described: Genie-based business case presented at Data + AI Summit
Positive
Turbulent_Half2548, Reddit commenter in r/databricks
When the commenter curates tables, filters, measures, and example questions for a team and shares the agent, non-technical colleagues ask real questions and get correct answers.
Published Jun 5, 2026self-described: Builds Genie spaces for non-technical colleagues
Consumer access works for business users chatting with data, but scheduling requires full Databricks SQL access, which would let them create spaces and dashboards and repeat the self-serve BI sprawl.
Published Jun 2, 2026self-described: Rolling Genie out to business users with consumer access
IWConnect's analyst team uses Genie spaces for profiling and before-and-after pipeline checks, saving about 3 hours per data quality investigation once metadata was in place. On a poorly documented dataset, a hidden many-to-many join produced a wrong number with no warning, so the team reads the SQL before sharing any result.
"Earlier, we asked Genie a similar question on a poorly documented dataset and shared a wrong number with confidence."
Excerpt, Marija Ristevska
"Time saved: ~3 hours per investigation, but only after metadata setup."
Same speaker
Published Apr 7, 2026IWConnect's business analyst team using Genie spaces for data quality checks, pipeline validation, and a source switch
Mixed
Glittering_Okra2002, Reddit poster in r/databricks
Their team's Genie chatbot for managers works well inside Databricks, but bringing it into Microsoft Teams through Copilot Studio or AI Foundry has been painful.
Published Dec 18, 2025self-described: Internal chatbot for managers to query report data
Positive
angryapathetic, Reddit commenter in r/databricks, consultant
Their team put a Genie space over the same star schema that feeds a Power BI report; the two reconcile, though key Power BI measures had to be copied into Genie's instructions.
Published Dec 13, 2025self-described: Genie space built to complement a Power BI report
Positive
randomName77777777, Reddit commenter in r/databricks
Their team has had success and plans a wider rollout; trusted assets give uniform answers, and spaces need ongoing work such as answering review requests and adding prompts against drift.
Published Dec 6, 2025self-described: Team planning a wider rollout
Their team stood up document question answering for the business with Genie over a vector search index. A Teams bot serves it and shows the SQL and rows behind each answer.
Published Jun 13, 2025self-described: Business-facing Genie served through a Teams bot
After a pilot, the poster found that Genie cannot see the rows its SQL returns, so it cannot explain results, and calls it a SQL generator, which falls short of intelligent analytics.
Published Jun 12, 2025self-described: Pilot with business end users
Their company keeps a Genie agent in Databricks as shared context, so personal agents ask Genie before they ask colleagues, with fewer pings and faster answers.
Published Oct 17, 2026self-described: Company using Databricks as shared context, with personal agents that query Genie
Their team stood up document question answering for the business with Genie over a vector search index. A Teams bot serves it and shows the SQL and rows behind each answer.
Published Jun 13, 2025self-described: Business-facing Genie served through a Teams bot
Building a Teams bot on the Genie API for stakeholders, the poster can configure the Genie space only through the UI and wants version control and approvals.
Published Jul 27, 2025self-described: Building a Teams bot on the Genie API for stakeholders
Mixed or negative, 3
Mixed
Glittering_Okra2002, Reddit poster in r/databricks
Their team's Genie chatbot for managers works well inside Databricks, but bringing it into Microsoft Teams through Copilot Studio or AI Foundry has been painful.
Published Dec 18, 2025self-described: Internal chatbot for managers to query report data
Their team connected a Genie space to Teams through Microsoft Foundry and an Azure bot, and hit problems with long-running requests that needed code changes.
Published Dec 18, 2025self-described: Connected Genie to Teams through Foundry and an Azure bot
Positive
anonymous_orpington, Reddit commenter in r/databricks
The commenter used Agent mode in Genie spaces to help clinical trial researchers ask more complex questions and go deeper, though the API did not support Agent mode at the time.
Published Jun 27, 2026self-described: Clinical trial researchers using Agent mode
A bundle that declares a Genie space fails on a fresh environment because its source tables must already exist. Unity Catalog still lets a referenced table be dropped, which leaves the space pointing at nothing.
Published Sep 18, 2026self-described: Team deploying Genie spaces with Databricks Asset Bundles to new feature-branch targets
Building a Teams bot on the Genie API for stakeholders, the poster can configure the Genie space only through the UI and wants version control and approvals.
Published Jul 27, 2025self-described: Building a Teams bot on the Genie API for stakeholders
Mixed
ihateticklesonmytoes, Reddit commenter in r/databricks
Their team has pressed its Databricks rep for deployable Genie spaces and packages the workflows behind the Genie datasets in a bundle until spaces can be added.
Published Jul 27, 2025self-described: Team packaging Genie datasets in asset bundles
Agrees that deployment is the biggest issue the commenter has had with Genie: the team cannot follow its standard testing and deploy workflow without heavy manual work.
Published Jun 21, 2025self-described: Team with a standard test and deploy workflow
Their SaaS company looked at Genie but serves 200 customer schemas, saw no way to deploy a space from code, and later built its own natural-language query tool.
Published Jun 12, 2025self-described: Evaluated Genie for a multi-tenant SaaS data mart
Mixed
mehulbhuva, Reddit poster in r/databricks, author of a SQLServerCentral article on Genie spaces
After eight months with 500+ sales users, the commenter warns the failure mode is a believable wrong number caught only by finance. Column comments, one pre-joined view, SQL expressions, and examples fixed it, but none of the config lives in git.
Published Sep 9, 2026self-described: Genie space live for 500+ sales users for 8 months
Their team versions Genie Agents by exporting the serialized space and deploying it through an Azure DevOps pipeline and the REST API.
Published Oct 7, 2026self-described: Team building an agent composed of Genie Agents
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Genie Agents can now be defined, deployed, and versioned with Declarative Automation Bundles, and management APIs create and update agents for CI/CD. Curate an effective Genie Agent
Among their clients, ungoverned creation of apps and Genie spaces eats into budgets, so the commenter recommends a platform admin team controlling creation.
Published Jul 7, 2026self-described: Clients building Genie spaces and apps
Mixed
Dissident-Contrarian, Reddit poster in r/databricks
Their team, focused on Genie spaces, could not tell how many DBUs one question would consume at US$0.070 per DBU after the pricing change was announced.
Published Jun 14, 2026self-described: Team focused on Genie spaces for AI/BI chat
Costing a Genie space for a business case, the commenter could not tie the extra cost of AI functions and serving endpoints back to the space short of one warehouse per space.
Published Mar 19, 2026self-described: Costing a Genie space for a business case
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Genie One and Genie Agents usage by named users is free until January 31, 2027. From February 1, 2027 each user gets 150 free DBUs a month, then pays US$0.070 per DBU on AWS US East, with SQL warehouse compute billed separately. Genie pricing
Questions the sources split on, with the count on each side.
Evidence remains mixed
Can business users rely on Genie's answers without review?
25
Directly, 2 sources
Some say business users stop rechecking figures once verified answers and curated context are in place.
With review, 5 sources
Others say wrong numbers still need an expert or finance to catch them, and users need training first.
Evidence remains mixed
Does Genie replace a team's BI dashboards?
32
Alongside BI, 3 sources
Most keep Power BI or AI/BI dashboards for official reporting and use Genie for follow-up and ad hoc questions.
Replaces BI, 2 sources
A few say users stop going back to dashboards, or that Genie let them drop a separate visualization tool.
The evidence
Whose experience this is
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on Leaders and teams rolling it out.
Leaders and teams rolling it out
49 sources. Accounts from data teams and departments, including consultants delivering Genie and leaders deciding business-user access.
Individual users
25 sources. Accounts from individual analysts and engineers trying Genie for their own work.
All users
74 sources. All reviewed accounts, combining individual tests with team and client rollouts. Their conclusions differ.
74 sources from practitioners, by the context they work in. Filled rows count for this group.
Individual userOne person using it for their own work25 sources
Emphasizes Answer quality, quick setup, and UI churn
Small team2 to 10 people sharing itNo sources from this setting yet
DepartmentA department, or a named company's team42 sources, counted here
Emphasizes Curated context, deployment as code, and cost after usage billing
IT & leadershipIT and business leaders deciding the rollout4 sources, counted here
Emphasizes Access and sprawl when business users get Genie
Organization-wideCompany-wide rollout3 sources, counted here
Emphasizes UI churn for company-wide Genie One users
What changes with scale. Individual users talk most about answer quality and how quickly an agent comes together. Team and client accounts shift to the curation behind good answers, deployment outside the UI, and cost. A Reddit poster whose whole company uses Genie One asks for a stable interface. Databricks' Summit pages describe Atlassian, GSK, and Virgin Atlantic gating each agent on a benchmark and signed-off metric views.
Where the sources come from
Where this group's sources were published.
Counted for Leaders and teams rolling it out, from 49 sources. Change group
68 sources for this group, 19 of them documentation
Data Communities, GitHub & X41, 60% of 68 sources
Product Documentation19, 28% of 68 sources
Blogs & Newsletters6, 9% of 68 sources
Talks & Podcasts2, 3% of 68 sources
Every first-hand source is dated 2025 or later. Sources that depend on a renamed feature, a since-added API, or billing terms Databricks has changed stay in the record, marked Needs a recheck.
Removes 14 non-English posts and a Medium lab exercise by an author without a full name, and keeps a SunnyData post under its named author.
The review holds 74 first-hand sources from Feb 18, 2025 to Oct 17, 2026.
Shows a finding on a page only when at least 5 sources from 3 different authors discuss it, and a disagreement only with at least 2 sources on each side.
Agent Mode (3 sources) has fewer than 5 sources from 3 authors, so it appears only in Evidence & Methodology. Data Scope Limits (5) reaches that bar only across all accounts.
Checks every documentation page against Databricks' current documentation and Genie pricing.
Oct 25, 2026: adds 3 sources from a newsletter, GitHub, and X, and cites Databricks' session pages for the Atlassian, GSK, and Virgin Atlantic talks.
Oct 26, 2026: adds named data leaders and teams at IWConnect, Okube, Headspace, Devoteam and Cleartelligence, each with the role stated on a first-party page.
Oct 26, 2026: adds named data leaders and teams at IWConnect, Okube, Headspace, Devoteam and Cleartelligence, each with the role a first-party page states.
Method
A running review of what people using Databricks Genie at work report, from individual users to company-wide rollouts. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Who counts
Leaders and teams rolling it out
Small team, Department, IT & leadership, Organization-wide
Individual users
Individual user
All users
Everyone in the leaders and teams and individual users groups
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
How the numbers work
Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among IT and business leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, leaders and teams read +41 positive (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
Method change, Oct 30, 2026. GILD changed how practitioner sentiment counts, to one vote per author. Weighted, it read +41 Positive; with one vote per author it reads +36 Positive. No evidence changed.
Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
Disagreements. The count on each side. GILD names no winner and gives no share of all users.
Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.
Labels on a source
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Documented
Stated in official documentation.
Reported
A practitioner's account of their own use.
Measured
Backed by the source's own measurements, such as a comparative test or tracked team metrics.
GILD analysis
GILD's check of a claim against official documentation.
Current
Describes the product as it is now.
Still applicable
Older, and the behavior or lesson still holds.
Needs a recheck
May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
Out of date
No longer accurate. Kept in the record; counts toward nothing current.
Flagged for a recheck, of the sources that take a side: leaders and teams 10 of 41, individual users 5 of 25, all users 15 of 66.
Limits
These figures count reviewed public sources. They are not a customer survey. r/databricks supplies 61 of 74 sources, read through the Arctic Shift archive. GILD kept first-hand accounts and excluded Databricks employees and competitor promotions. Databricks' Data + AI Summit 2026 session pages for the Atlassian, GSK, and Virgin Atlantic talks are cited as Databricks pages and count toward no figure. Genie Code, the developer assistant, is outside this review.
Genie changed names during the window: Genie spaces became Genie Agents, Databricks One became Genie One, and the research agent became Agent mode. Sources that depend on missing APIs or bundle support, or on billing terms Databricks has since changed, are marked Needs a recheck.
Every count, and the sources behind it
17 findings for 3 groups
Each row opens its sources for the group you are reading.
GILD's checks of claims against official documentation, kept apart from the source counts.
Believable Wrong Numbers. Databricks documents that Genie can return different outputs for the same prompt. It offers benchmarks of up to 500 questions per agent, scored against a SQL answer in Chat mode or by an LLM judge in Agent mode. Test and monitor a Genie Agent, checked Oct 12, 2026
Curation Workload. Databricks tells curators to treat Genie as a new analyst, start with five or fewer tables, and prefer SQL expressions and example SQL over text instructions. Curate an effective Genie Agent, checked Oct 12, 2026
Deployment as Code. Genie Agents can now be defined, deployed, and versioned with Declarative Automation Bundles, and management APIs create and update agents for CI/CD. Curate an effective Genie Agent, checked Oct 12, 2026
Cost & Billing. Genie One and Genie Agents usage by named users is free until January 31, 2027. From February 1, 2027 each user gets 150 free DBUs a month, then pays US$0.070 per DBU on AWS US East, with SQL warehouse compute billed separately. Genie pricing, checked Oct 12, 2026
Data Scope Limits. A Genie Agent holds up to 50 Unity Catalog tables, views, or metric views; Chat mode works on structured data only, and Agent mode can read files in volumes as a Beta. Create and manage a Genie Agent, checked Oct 12, 2026
Renames & UI Changes. Databricks' documentation notes that Genie Agents were formerly Genie Spaces and that Genie One was previously Databricks One. Genie One, checked Oct 12, 2026