# 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.