> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-admin-guide/v20-de-de/berichterstellung/microsoft-sql-server-installieren/microsoft-sql-server-2017-oder-2019-installieren.md).

# Microsoft SQL Server 2017 oder 2019 installieren

Mit Microsoft SQL Server 2017 und 2019 können Sie die Datenbank-Engine und SQL Server Reporting Services (SSRS) auf separaten Hosts installieren. Parallels RAS 17.1 (und neuer) unterstützt dieses Berichterstellungsszenario und bietet Ihnen die Möglichkeit, SQL Server Reporting Services und die SQL Server-Datenbank-Engine auf separaten Hosts zu nutzen.

Für eine schrittweise Anleitung zur Installation und Konfiguration von Parallels RAS Reporting Service mit SQL Server 2019 und Microsoft SSRS 2019 lesen Sie bitte die folgenden Artikel der Parallels-Wissensdatenbank:

* **Microsoft SQL Server 2017 und 2019 – Installation auf einem Server**: <https://kb.parallels.com/125164>.
* **Microsoft SQL Server 2017 und 2019 – Installation auf mehreren Servern**: <https://kb.parallels.com/125156>.


---

# 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.parallels.com/landing/ras-admin-guide/v20-de-de/berichterstellung/microsoft-sql-server-installieren/microsoft-sql-server-2017-oder-2019-installieren.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.