Schema migrations

If you use the Tosca Administration Console, you can trigger the migration directly in the console.

Prepare for the migration

Since the console is part of Tosca Server, you need to perform these preparatory steps:

1. Install Tosca2024.2 on the server machine.

2. Upgrade Tosca Server.

Perform the migration

For detailed instructions, check out "Migrate projects with the Tosca Administration Console".

If you don't use the console, you have to migrate your schema manually.

Prepare for the migration

To prepare for the manual migration, perform these actions:

• Get a connection string to your repository database. The user in this connection string must have ALTER, CREATE, and DELETE rights to create tables, delete indexes, and create new indexes.

• Ask all users to check in their local changes. Migrations run on the repository version of all objects. If you migrate objects that are checked out by other users, you lose all local changes.

• Create a backup of your database. If the migration fails, you must load the backup before you can make another migration attempt.

Perform the migration

To migrate a schema, follow these steps:

1. Go to %COMMANDER_HOME%.

2. Open the Command Prompt window and run the following command:

   DbRepositorySchemaMigrator.exe "<database type>" "[schema name]" "[tablespace name]" "<connection string>"

   • Replace <database type> with the database type of your repository: Oracle, MS SQL Server, DB2, or SQLite.

   • Optionally, replace [schema name] with the database schema name.

   • Optionally, replace [tablespace name] with the tablespace name of your database. The name of the tablespace depends on which database you use: Tablespace (DB2), Userspace (Oracle), FileGroup (MS SQL).

   • Replace <connection string> with a connection string to connect to your repository database. For SQLite repositories, enter the absolute path to the CommonRepository.db file.

   • Optionally, add -s at the end of your command to perform the migration in silent mode, without user interaction.

Here are two examples for migration commands. This command migrates the schema of your SQLite repository database: DbRepositorySchemaMigrator.exe "SQLite" "C:\Tosca_Projects\Tosca_CommonRepositories\GUItests\CommonRepository\CommonRepository.db" This command migrates the schema of your DB2 database in silent mode. The schema name is my_common_schema: DbRepositorySchemaMigrator.exe "DB2" "my_common_schema" "Server=111.111.111.111:5050;Database=myDataBase;UID=myUsername;PWD=myPassword;" -s

Once it's done, DbRepositorySchemaMigrator.exe displays a message that indicates whether the migration was successful or not. For detailed migration results, check the log file SchemaMigration_<File name>.txt, located at %APPDATA%\TRICENTIS\TOSCA TestSuite\7.0.0\Temp\TCTempLog.

You can now open your multi-user workspaces in Tosca. Tosca migrates workspaces when you open them for the first time after the schema migration.