> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/9.3-analytics/data-source-wizard-cp-overview/before-using-the-data-source-wizard.md).

# Before using the Data Source Wizard

The Data Source Wizard is intended for prototyping or as a starting point for Pentaho Analysis and Pentaho Metadata models used with Interactive Reports, Analyzer reports, and dashboards. As a best practice, re-create or edit these models with the Schema Workbench or Metadata Editor to ensure query performance and to leverage enhanced features when used in production environments.

**CAUTION:**

Data sources created with the Data Source Wizard are not supported for use in a production environment.

Because of the following reasons, data sources created with the Data Source Wizard are not supported for use in a production environment:

* Data sources created with the Data Source Wizard cannot be secured using Pentaho roles, as per the security configuration.
* They are not optimized for performance.
* They may not conform to design best practices.


---

# 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.pentaho.com/pba/9.3-analytics/data-source-wizard-cp-overview/before-using-the-data-source-wizard.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.