> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/app/setting-up-your-database/databricks/before-you-create-a-databricks-workspace/databricks-config-create-dest-schema.md).

# Configuring the destination database schema creation

By default, during data generation to Databricks Delta tables, Structural creates the database schema for the destination database tables, then populates the database tables based on the workspace configuration.

To manage the database schema yourself, set the [environment setting](/app/admin/environment-variables-setting.md) `TONIC_DATABRICKS_SKIP_CREATE_DB` to `true`. You can configure `TONIC_DATABRICKS_SKIP_CREATE_DB` from the **Environment Settings** tab on **Structural Settings**.

When `TONIC_DATABRICKS_SKIP_CREATE_DB` is true, then Structural does not create the destination database schema. Before you run data generation, you must create the destination database schema.

Note that you can override this setting in individual workspaces. For more information, go to [Advanced workspace overrides](/app/workspace/workspace-configuration-settings/advanced-overrides.md).

For a diagram of the data generation process when you manage the destination schema, go to [Data generation process](/app/workflows/data-generation-run-job/data-generation-process.md#data-process-customer-schema).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tonic.ai/app/setting-up-your-database/databricks/before-you-create-a-databricks-workspace/databricks-config-create-dest-schema.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.