Redgate Flyway

If no shadow database is configured, you will be prompted to configure it from the GUI when navigating to the Generate Migrations tab.
From this screen you can enter the connection details for your shadow database, including authentication type and credentials.
1. By default, your password is stored in your operating systems built-in credential storage tool.
2. By default, your shadow database information is stored to the user settings.
  When setting the shadow database/schema connection, ensure it isn't an important database/schema as this may be cleaned and rebuilt when generating migration scripts in Flyway Desktop. There is a checkbox that you must explicitly click to confirm that all the data and schema in the shadow database can be erased. You will also need to make sure that you have sufficient permissions to clean the database/schema.
Click Test connection or Test and save to close the dialog and start tracking changes to your development database.
Once it is configured, the connection details can be altered via the Environments page or the Settings Cog, which will display the following options.

You can add a shadow database environment configuration to your toml configuration file or user configuration file as follows:

[environments.shadow]
url = "jdbc:sqlserver://localhost;authentication=sqlPassword;databaseName=Shadow;encrypt=true;trustServerCertificate=true"
user = "sa"
password = "..."

Automatically create user specific shadow databases

If all of your developers have the same shadow connection details, this can be saved in the flyway.toml project file to make setup easier. Just save the database details to the project settings, which are stored in the flyway.toml project file and gets committed and shared in version control. For example, every developer has 2 databases (projectName and projectName_shadow) on their localhost.

If you are using a shared server for your shadow database, the project can be setup to create a shadow database for each user in the flyway.toml project file using the UserName environment variable on Windows. Make sure to update the provisioner to be "create-database" so this database will be created as new team members join the project. The user would need to have permissions to create a database on the server for this to work

[environments.shadow] url="jdbc:sqlserver://localhost;databaseName=<projectName>_shadow_${env.UserName:a};encrypt=mandatory;trustServerCertificate=true" provisioner="create-database"

${env.UserName:a} gets expanded to the user's username. :a removes any non-ASCII characters so special characters in a name are not a concern. For example, this would create a database named projectName_shadow_myUserName.

Hint - start your shadow database names with a z

Some users like to name their shadows as z_<DbName>_shadow_<DevName>. This is especially true on a shared centralized development server so all these databases appear at the end of the list. If you are using SQL Server and SSMS, you can filter out and databases whose name contain "_shadow" from the Object Explorer view.

Next steps

Pick one of:

Validate migration deployment
Generate migrations (note that this validates migration deployment as part of comparing against migrations)
Baseline (prerequisite for generating migrations if you do not have any yet, unless working on a completely greenfield database)

Redgate Flyway

Tutorial - Configure the shadow database

Automatically create user specific shadow databases

Hint - start your shadow database names with a z

Next steps