> 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.md).

# Data Source Wizard

Before you can create Pentaho reports and analysis, the Pentaho Server needs to know where to find your data and how to connect to it, what data you want to use, how the data is structured, and what the data is like. The Data Source Wizard helps you define a data source that contains this information and guides you through the creation of your first [relational](http://en.wikipedia.org/wiki/Relational_model) or [multidimensional](http://en.wikipedia.org/wiki/Multidimensional_database#Multidimensional_databases) data models for use in creating reports and analysis.

After you define a data source, you can make it available to people who create reports and analysis so they can simply pick the data source they want to use from a list and begin creating their reports or analysis. One data source can be used by any number of reports or analysis.


---

# 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.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.