Genie Space Instructions, Example SQL, and Trusted Assets

1.Domain-specific instructions: SQL first, text last

Once the data is attached, you teach Genie your business. You can do this in three ways, and Databricks ranks them clearly. Use SQL expressions in the knowledge store for common business terms, such as metrics, filters and dimensions. Use example SQL queries for complex or multi-part questions. Use plain-text instructions only for guidance that cannot be written as SQL. SQL-based definitions are more reliable and easier to maintain than text.

Write text instructions on the Text tab under Configure. General instructions apply to every question. If something applies only to some questions, put it in an example query, a function, or a table comment instead. Keep the list short: too many instructions make it harder for Genie to know which ones matter most, especially in long conversations. A space can hold 100 instructions. Each example SQL query counts as one, each SQL function counts as one, and the whole General instructions block counts as one. The docs give this example of good general instructions:

- **Company-specific business information**:
  - Fiscal year starts in February, for example fiscal year 26 or FY26 is February 1, 2026 through January 31, 2027
- **Formatting**:
  - Always respond in Spanish
  - If no other specification exists, round all decimals to two places
  - Omit commas in results for any column including "Id" or "id" or "\_id"

Vague instructions don't help. To make Genie ask a clarifying question, say exactly when to ask and what to ask. Put these instructions at the end of your general instructions so Genie gives them priority. To change how Genie writes its summaries, such as the language or the citing of tables, add a section titled "Instructions you must follow when providing summaries". Only text instructions affect summaries. Finally, keep all your guidance consistent. If a text instruction says to round to two decimals, your example SQL must also round to two decimals.

Sources12

2.Example SQL queries and suggested queries

You add example queries on the Examples tab. Each one is a question paired with the SQL that answers it. For the title, use the most common way a user would phrase the question, because that helps Genie match new questions to it. If a question matches, Genie can use the query as is. If a question is only similar, Genie learns from the query's structure. Choose examples that show logic specific to your organization, like this pipeline definition:

-- Return our current total open pipeline by region.
  -- Opportunities are only considered pipelines if they are tagged as such.
  SELECT
    a.region__c AS `Region`,
    sum(o.amount) AS `Open Pipeline`
  FROM
    sales.crm.opportunity o
    JOIN sales.crm.accounts a ON o.accountid = a.id
  WHERE
    o.forecastcategory = 'Pipeline' AND
    o.stagename NOT ILIKE '%closed%'
  GROUP BY ALL;

You don't have to write every example yourself. When you add data, Genie searches for popular workspace queries on those tables that you have at least CAN VIEW on. If it finds some, it shows a Review notification on the Data tab. In the Review Suggested Queries dialog, you can edit the question title, but the SQL in the Code field is read-only. Click Accept or Reject for each one. Accepted queries become fully editable examples. Genie suggests queries only for tables attached to the space. If you built a view just for Genie, queries against the original source table won't be suggested. To tell Genie when an example applies, add Usage guidance to it.

Sources23

3.Vetting queries as Trusted Assets

Trusted Assets are how you vet a query. When Genie answers using one, the response is marked as a verified answer, which gives users extra confidence. There are two kinds. The first is a parameterized example SQL query. Genie marks the answer as verified only when it uses the query's exact text, and users can then change the parameter value and run it again. To add a parameter, click Add parameter or type a colon followed by a name (:parameter_name) in the query editor. Then fill in the parameter details:

Choose the data type carefully. If a value doesn't match the type, Genie treats it as the wrong type, and the results can be wrong. The second kind of Trusted Asset is a SQL function registered in Unity Catalog. Use one when the logic is too complex for a static or parameterized query. Genie supports scalar functions and table-valued functions. Genie can call a function with values from the user's question, but it cannot see or change the SQL inside it. That makes functions a good fit for logic you want to keep hidden or protected.

Two permission rules apply. To add or remove Trusted Assets, you need at least CAN EDIT on the space. Users of the space need EXECUTE on every SQL function used as a Trusted Asset. Once your assets are in place, be the space's first user. Ask realistic questions, read the SQL Genie generates, and adjust your instructions and examples until the answers are reliable.

Sources21

Exam traps

Each one states something that sounds right. Open it to see what is actually true.

1. 1.Every example SQL query you add to a space is a Trusted Asset and produces a verified answer.Why is that wrong?

   Only parameterized example queries and Unity Catalog SQL functions are Trusted Assets. The answer is marked verified only when Genie uses the exact text of a parameterized query.

   Covered in Vetting queries as Trusted Assets

2. 2.Text instructions are the main way to define business metrics such as revenue or gross margin in a Genie space.Why is that wrong?

   Metrics should be defined as SQL expressions, and complex patterns as example SQL. Text instructions are a last resort.

   Covered in Domain-specific instructions: SQL first, text last