> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/connectors/areas/business-systems/ifs-applications/ifs-odata/configuring-databases.md).

# Configuring databases

The IFS OData Connector can use sqlite (default) Sql Server or Postgres as database for its internal data. It can (but does not have to) use a separate database for it's communication logs. 

This is controlled via the appsettings.xml file with on-premises hosting and typically via app service configuration when hosting in Azure. If any of these values are changed, the service must be restarted for them to have an effect. 

**DbKind** controls what kind of database to use for everything except communication logs, allowed values: sqlite,sqlserver,postgres 

**DbKindCommLog** controls  controls what kind of database to use for http communication logs.

**ConnectionStrings,** **LocalDb** and **CommLogDb** respectively must be a valid connection string to selected database. 

If **DbKindCommLog** and **CommLogDb** connection strings are not defined, the **DbKind** and **LocalDb** database settings will be used for communication logs as well as other data. 

Example with communication log stored in sql server and other data in sqlite. Other parts of appsettings.xml omitted for clarity. 

```xml
 <DbKind>sqlite</DbKind>
 <DbKindCommLog>sqlserver</DbKindCommLog>
	
 <ConnectionStrings>
     <LocalDb>Data Source=db.db</LocalDb>
     <CommLogDb>Server=databaserServerX;Database=commlog;User Id=dbuser;Password=secret;Encrypt=False</CommLogDb>
 </ConnectionStrings>
```


---

# 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://help.novacuraflow.com/connectors/areas/business-systems/ifs-applications/ifs-odata/configuring-databases.md?ask=<question>&goal=<user_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.