> 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-job-entries-reference-overview/bulk-load-into-azure-sql-db/options-azure-sql-db-bulk/input-tab-azure-sql-db-bulk.md).

# Input tab

![Bulk load into Azure SQL DB Input tab](/files/UEekeXqOtrKVZKA7zrMM)

Use the options in this tab to define your input source for the Azure SQL database:

| Option                             | Description                                                                                                                                                                                                                                                                                                                                                                                                                                |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Source**                         | Specify the VFS URL of the data to import. The URL can point to a file or a folder in Azure Data Lake Storage. The URL must begin with `pvfs://` and must specify the bucket and object you want to load. See [Pentaho address to a VFS connection](/pdia-data-integration/9.3-data-integration/data-integration-perspective-in-the-pdi-client/virtual-file-system-browser/pentaho-address-to-a-vfs-connection-open-a-transformation.md) . |
| **What file type is your source?** | Select the file type of the input source. Must be a CSV file.                                                                                                                                                                                                                                                                                                                                                                              |
| **Delimited text settings**        | <p>Specify the following settings for a delimited text file:</p><ul><li><strong>Delimiter</strong></li></ul><p>Specify the character used to separate a data field. The default is semicolon (;).</p><ul><li><strong>First line is column names</strong></li></ul><p>Select <strong>Yes</strong> if the first line in the file contains the column names.</p>                                                                              |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-job-entries-reference-overview/bulk-load-into-azure-sql-db/options-azure-sql-db-bulk/input-tab-azure-sql-db-bulk.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.