> 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/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/add-sequence-step-article/database-generated-sequence-add-sequence-step.md).
# Database generated sequence
The following table contains options for generating a sequence from a database:
| Option | Description |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Use DB to generate the sequence?** | Select this check box if you want the sequence to be driven by a database sequence.
Use counter to calculate sequence? is automatically selected if this check box is cleared. Use counter to calculate sequence? is set by default.
|
| **Connection** | Select the connection to where your database sequence resides. If you do not have an existing connection, click either **New** or **Wizard**. If you need to modify an existing connection, click **Edit**. |
| **Schema name** (optional) | Specify the schema name of any related table. Click **Schemas** to select a schema within the database you specified for **Connection**. |
| **Sequence name** | Specify the name of the database sequence. Click **Sequences** to select a sequence within the database you specified for **Connection**. |
---
# 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/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/add-sequence-step-article/database-generated-sequence-add-sequence-step.md?ask=&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.