> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/convert-microsoft-sql-server-workspace-to-contained.md).

# Convert Microsoft SQL Server workspace to contained

Convert a Microsoft SQL Server workspace to contained in Remote Desktop Manager so authentication travels with the database.

Administrators might want to convert their Microsoft SQL Server workspace from non-contained to contained, allowing authentication to travel with the database instead of being managed at the server level.

{% hint style="danger" %}
A proper workspace backup strategy should be implemented to prevent possible data loss.
{% endhint %}

1. Configure your SQL Server to allow contained databases. Should the last command return an error message, use the `sp_who2` command to find the SPID of the open connections.
2. Create an administrator user for the SQL database.
3. Back in Remote Desktop Manager, in the ***General*** tab of your workspace, change the type to ***Microsoft Azure SQL***, and set a ***Username*** and ***Password***. Click ***Save***.
4. Go to the ***Advanced*** tab, click on ***More settings***, and set the ***Encrypt*** setting’s value to ***false***. Click ***Ok*** to close the window, then ***Save*** the modification.
5. Then, tick the ***Contained database user (recommended)*** checkbox every time you [create a new user](/rdm/ribbon-menu-bar/administration/user-management.md) for this workspace.


---

# 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.devolutions.net/rdm/knowledge-base/how-to-articles/convert-microsoft-sql-server-workspace-to-contained.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.