> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/writebackextreme/getting-started/setup/repository-database/sql-server.md).

# SQL server

To use SQL Server, an SQL-srv account has to be used as opposed to a Windows-authenticated (AD) account. Furthermore, the following is required:

1. Database host
2. (Optional) Database port
3. Database name
4. Database username
5. Database password

{% hint style="info" %}
Leave the username and password empty to use the local user of the system. When you do this, make sure to change the logon user of the service when running the application as service in the background to match this user.
{% endhint %}

{% hint style="info" %}
Using a host like machine01instance?\
Write it like this: machine01instance
{% endhint %}

{% hint style="danger" %}
Password **cannot** contain `$` signs.
{% endhint %}

<figure><img src="/files/WCZMQxr0FiWjq40OuAOr" alt=""><figcaption></figcaption></figure>

![](https://appsfortableau.infotopics.com/wp-content/uploads/2023/08/Screenshot-at-1-16.png)

<details>

<summary>SQLSTATE[08001]: SSL Provider: The certificate chain was issued by an authority that is not trusted</summary>

**Symptoms**

During installation or configuration, the extension cannot establish a database connection.\
Error messages may mention SSL/TLS, certificate trust, or “the certificate chain was issued by an authority that is not trusted.”

* Error message example:

  ```
  SQLSTATE[08001]: [Microsoft][ODBC Driver 18 for SQL Server]SSL Provider: 
  The certificate chain was issued by an authority that is not trusted.
  ```

**Cause**\
The SQL Server requires SSL encryption, but the certificate presented cannot be validated. This usually happens when:

* A self-signed certificate is being used, and the authority certificate is not trusted on the machine running WBE.
* The full certificate chain (including intermediates) is not installed.

**Solution**

1. If possible, install a certificate signed by a trusted Certificate Authority (CA).
2. If using a self-signed certificate, import the authority certificate into the **Trusted Root Certification Authorities** store on the server where WBE runs.
3. If the issue persists during installation, try the following steps:
   * Stop the WriteBackExtreme service.
   * Delete the **runtime** and **config** folders to reset the installation.
   * Restart the installation and re-enter database details.
   * Tick **Disable SSL certificate validation for the SQL Server database** to bypass the validation check.

</details>


---

# 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.infotopics.com/writebackextreme/getting-started/setup/repository-database/sql-server.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.
