# Database Connections
{% hint style="success" %}
**Who can use this feature?**
The **Database Connections** can be used by those with the **Builder** subscription plan.
For more details, see our [**pricing comparison matrix**](https://squirrel365.io/pricing/).
{% endhint %}
The **Database** Connections can be used to connect the Squirrel project to an external InfoBurst database.
There are two different **Database** connections:
* **Database Query** - queries the referenced database and returns the selected query.
* **Database Writeback** - writes back to the selected query and updates the information based on an insertion
## Common Database Connector Properties – Credentials
An Infoburst URL and login credentials are required to use the **Database** connectors. These can be obtained from the Infoburst webpage, as well as the URL port.
### Database Login Credentials
The '**Infoburst URL**' is used to access followed by a port to identify the specific environment.
After entering the URL, all that is needed is a '**Username**' and '**Password**'.
All three of the credential fields can be bound to cells in the spreadsheet.
***
## Mapping the data to the spreadsheet
After connecting to the database, the **DATA MAPPING** properties will populate which is where you can define the cache or cache query to be brought into Squirrel.
***
### Database Query
The **Database Query** DATA MAPPING properties will populate a list of the existing caches within the connected database. After making a selection, the dropdown will outline the number of caches selected.
The selected query will populate below the dropdown to bind its location to the spreadsheet. The **Destination** field will appear to bind the query to an area in the spreadsheet for the data to populate at runtime.
**Max Rows** will determine if there is a limit on the number of rows returned from the database.
{% hint style="info" %}
If the database contains parameters defined in the SQL code, a PARAMETER sub-drawer will populate in the DATA MAPPING drawer.
{% endhint %}
The Parameter inputs that appear will be labelled as the value defined in the Database SQL code.
***
### Database Writeback
The **Database Writeback** DATA MAPPING properties will populate a list of the existing cache queries within the connected database. After making a selection, a sub-drawer will populate labeled META DATA.
{% hint style="info" %}
If the database contains parameters defined in the SQL code, a PARAMETER sub-drawer will populate in the DATA MAPPING drawer.
{% endhint %}
The **FALLBACK STATEMENT** drawer defines a "backup" writeback that will execute only if the initial writeback statement fails. The property panel layout is the same as the original Writeback Statement.
The **QUERY ON SUCCESS** drawer is used to run a query if either of the above writeback statements succeeds.
***
## Triggering the connection
Like most connections, the properties panel has a **USAGE** drawer that provides control of the connector's triggers.
* **Refresh on Load** - as described, the connection will trigger and the data will be brought through to the spreadsheet on the load of the project. This can be previewed in Debug and Preview modes.
* **Refresh on Interval** - defines an Interval that the connection will refresh. When selected, an input will populate where a period of seconds can be defined for the connection to refresh.
* **Refresh on Cell Changes** - sets the trigger to refresh on the change of another cell. This property utilizes **Conditional Logic**. For more information on **Conditional Logic** and its uses, see [**this article**](https://learn.squirrel365.io/getting-started/dynamic-visibility#conditional-logic).
---
# Agent Instructions: 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:
```
GET https://learn.squirrel365.io/components-functions-and-connections/overview-2/infoburst/database-connections.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
