A series of key/value pairs of tokens can be passed to yuniql. During migration run, yuniql inspects all tokens in script files and replaces them. This is particulary useful in cases such as cross-database and linked-server queries where the databases and server names varies per environment.
The following script would fail when run in TEST where EMPLOYEEDB_DEV database does not exists but EMPLOYEEDB_TEST.
SELECT E.FirstName, E.LastName, E.Address, E.Email
FROM [EMPLOYEEDB_DEV].[dbo].[Employee] E
ORDER BY E.FirstName ASC
To resolve this, let’s pre-pare your script with token ${ENV-DBNAME-SUFFIX}. You can of course use whatever token name.
SELECT E.FirstName, E.LastName, E.Address, E.Email
FROM EMPLOYEEDB_${ENV-DBNAME-SUFFIX}.[dbo].[Employee] E
ORDER BY E.FirstName ASC
Pass the tokens when you run migration
yuniql run -k "ENV-DBNAME-SUFFIX=DEV"
yuniql run -k "ENV-DBNAME-SUFFIX=TEST"
yuniql run -k "ENV-DBNAME-SUFFIX=PROD"
You may also pass the tokens as a series of key/value pairs separated by comma.
yuniql run -k "token-key1=token-value1,token-key2=token-value2"
yuniql run -k "token-key1=token-value1" -k "token-key2=token-value2"
IMPORTANT: Tokens values are required parameters when at least one of script files is tokenized. Failure to get this token values from CLI or API will throw an exception and will fail the entire migration.
A working sample is available here for your reference https://github.com/rdagumampan/yuniql/tree/master/samples/sqlserver-all-features-sample/v1.00
Learn further
- Migrate via ASP.NET Core
- Migrate via Azure DevOps
- Migrate via Docker Container
- Migrate via Console Application
- Yuniql CLI Command Reference
- Bulk Import CSV Master Data
- Environment-aware Migration
Found bugs?
Help us improve further please create an issue.