Migrate the Galaxy database
- Last UpdatedJun 11, 2025
- 2 minute read
To migrate the database:
-
The IDE you use to migrate the database must be the current version.
-
The GR node must already be upgraded to the current version.
Make sure that all connections to the Galaxy database are closed before migrating the database.
After you migrate the Galaxy, deployed objects on a non-upgraded node are marked with pending software upgrade status.
SQL Server considerations
If the GR node contains less than the recommended RAM amount, system performance may be impacted as SQL Server will use more CPU to compensate for the lower amount of available memory. To improve system performance, set the SQL Server minimum memory (min server memory) to 1/3 of total physical memory. See Allocate Galaxy Repository Node Memory for additional information.
To migrate the Galaxy database
-
Start the IDE.
-
Connect to the Galaxy database to migrate. You are prompted to migrate it.
-
Follow the prompts to complete the migration.
Migration errors
Migration of a very large Galaxy may fail, with various (and sometimes misleading) warnings and errors displayed in the Logger. This is due to the Galaxy database transaction log expanding beyond its maximum allocated size.
Before making the changes described here, use the Event Viewer to check if the transaction log is full. If you confirm that the transaction log has exceeded its maximum file size restriction, remove the restriction as follows:
-
In SQL Server Management Studio, right click the Galaxy database, then select Properties on the shortcut menu.
-
In the Database Properties dialog, select the Files page.
-
Locate Log ... in the File Type column.
-
Click the More (...) button in the Autogrowth column on the same line.
-
In the Change Autogrowth for Base_Application_Server_log dialog, select the Unrestricted File Growth radio button under the Maximum File Size parameter, then click OK.
-
After the Galaxy migration is finished, repeat steps 1 through 5 to reinstate the file size limit on the transaction log.