> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/s2gw-installation-manual/quick_installation/migration_from_boomerang_2/using-migration-tool-with-own-sql-credentials.md).

# Using migration tool with own SQL credentials

There is a method to use the migration tool in the current version with the SQL credentials defined separately from B2 settings.

The xml file for standard SQL sa account settings where 

```
SQL user: sa
Password: ICU_ROOT_11
```

looks as follows: 

```
<?xml version="1.0" encoding="utf-8"?>
<RemoteDatabaseConfig xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <strHost>192.168.61.252</strHost>
  <strUsername>sa</strUsername>
  <strPassword>NXDa2+dKCZe1lSfXKPmYbg==</strPassword>
  <port>1433</port>
  <bUseRemote>true</bUseRemote>
  <instanceName>ICUDB</instanceName>
</RemoteDatabaseConfig>
```

&#x20;If the default SQL user credentials were used then the only tag to modify is \<strHost>.

The DatabaseConfig.xml and file called Boomerang2.exe (it may be any file with such a name) shall be placed in a directory which then shall be selected as the source of information for B2 database access. This will create a correct JSON file.


---

# 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.boomerang3.com/s2gw-installation-manual/quick_installation/migration_from_boomerang_2/using-migration-tool-with-own-sql-credentials.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.