> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/editable/getting-data-into-editable/connect-to-data/get-data.md). # Get data In this section, we will get the data by connecting to a database through **DirectQuery mode in Power BI.** {% hint style="info" %} If you're looking to create a table from scratch or import spreadsheet data, you can refer to [this section](/editable/getting-data-into-editable/create-a-table.md). {% endhint %} 1. To load the required data into Power BI, select **Get data** on the Home tab**.** The procedure is the same as importing any data into Power BI. In this example, we'll choose 'Azure SQL database'.

2. In the SQL Server database dialog box, enter the **Server** and **Database (optional)** names, and make sure the **Data Connectivity mode** is set to **DirectQuery**.

{% hint style="info" %} EDITable connects to data sources only through **DirectQuery.** This ensures the report always uses the current data. {% endhint %} **Note:** For any database connection, make sure to select DirectQuery mode. Please find below the image that appears when you select a Snowflake database.

3. Select the required table in the Navigator to preview the data and click **Load.** No transformation is required for this data as it is already prepared.

4. You might get a warning pop-up depending on the connection you choose. Since you will be connecting to your trusted source, you can proceed by clicking **OK** to load the data. You can now view the 'EmployeeDemo' table in the Data pane. Note that the connection is through DirectQuery.

Now that we have connected to the database, the next step is to assign the fields in the Visualizations pane. --- # 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.inforiver.com/editable/getting-data-into-editable/connect-to-data/get-data.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.