> 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/before-you-begin-azure-sql-db-bulk.md).

# Before you begin

Before using the **Bulk load into Azure SQL DB** job entry in PDI, you must have the following items:

* An Azure account.
* A connection to the Azure SQL database in which to load your data. For more information, see the **Install Pentaho Data Integration and Analytics** document.
* A VFS connection to Azure Data Lake Storage.
* A table and schema set up in the database where you want to place your data. The table must have defined all the columns you need. On the first use, you need to create the table.

**Note:** The INSERT and ADMINISTER DATABASE BULK OPERATIONS permissions are required in the Azure SQL database to use the **Bulk Load into Azure SQL DB** job entry.


---

# 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/before-you-begin-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.