to - this should be a .zip file (Required) --project (-P) : The path to the *.conf file created by Redgate Change Control … for connecti
to - this should be a .zip file (Required) --project (-P) : The path to the *.conf file created by Redgate Change Control … for connecti
run --rm -v $CI_PROJECT_DIR:/project/ redgate/change-automation:$RCA_VERSION build -v -P /project/demo-project/demo-project.conf -t $CI_D
returnStatus: true, label: "Build", script: "rca build -P \"${ProjectPath}\" -t ${CiDatabaseJdbc} -o \"${BuildArtifactPath}\" -c -f -v -u
run --rm -v $CI_PROJECT_DIR:/project/ redgate/change-automation:$RCA_VERSION build -v -P /project/demo-project/demo-project.conf -t $CI_D
returnStatus: true, label: "Build", script: "rca build -P \"${ProjectPath}\" -t ${CiDatabaseJdbc} -o \"${BuildArtifactPath}\" -c -f -v -u
"$(Pipeline.Workspace)/s:/app/project" -v "$(Build.ArtifactStagingDirectory):/app/output" redgate/change-automation:$(RCA_IMAGE_VERSION)
"$(Pipeline.Workspace)/s:/app/project" -v "$(Build.ArtifactStagingDirectory):/app/output" redgate/change-automation:$(RCA_IMAGE_VERSION)
(-P) : The path to the *.conf file created by Redgate Change Control … be specified here or in the environment variable BUILD_DATABASE_U
. If no user is specified, Windows authentication will be used /password:<password> /p The user password /outfile:<file name> /out The fil
/scg/sql-code-analysis-documentation/code-analysis-for-sql-server-command-line
sign to turn off a default option. $staging = New-DlmDatabaseConnection -ServerInstance 'staging01\sql2012' -Database 'Staging' -Username
artifacts necessary to prepare a release. build: stage: build script: docker run --rm -v $CI_PROJECT_DIR:/project/ redgate/change-automat
/dso/redgate-change-automation/example-ci-cd-pipelines/gitlab
(for example, <i>, <b>, <p>, <ul>, <li>, <h1>, h2>, <pre>) for formatting the text in the help window. In most cases, you will want to id
/ssm1/xml-schema-reference-for-script-files/types-of-control
Analysis for Oracle; Checking for Invalid Objects" def status status = bat returnStatus: true, label: "Build", script: "rca build -P \"${
/dso/redgate-change-automation/example-ci-cd-pipelines/jenkins
" -Username "sa" -Password "p@ssw0rd" $DB2 = New-DlmDatabaseConnection -ServerInstance "your-server\sql2014" -Database "WidgetProduction"
(for example, <i>, <b>, <p>, <ul>, <li>, <h1>, h2>, <pre>) for formatting the text in the help window. In most cases, you will want to id
/ssm2/xml-schema-reference-for-script-files/types-of-control
"P@ssw0rd" Sync-DlmDatabaseSchema -Source $scriptsFolder -Target $test This example show how to update a test database to match a scripts
\sql2012" -Database "Staging" -Username "sa" -Password "P@ssw0rd" $test = New-DlmDatabaseConnection -ServerInstance "test01\sql2012" -Data
/dlma1/using-sql-compare-options-with-dlm-automation-cmdlets
/change-automation:$(RCA_IMAGE_VERSION) build -v \ -P /app/project/citi-demo.conf \ -t $(CI_DB_JDBC) \ -o /app/output/buildArtifact.zip \
/dso/redgate-change-automation/example-ci-cd-pipelines/azure-devops
", "-U", "MyUser", "-P", "MyPassword", "-d", "MyDatabase", "-Q", "SELECT 1"] interval: 10s retries: 20 The build step is here being contro
'Staging' -Username 'sa' -Password 'P@ssw0rd' $test = New-DlmDatabaseConnection -ServerInstance 'test01\sql2012' -Database 'Test' -Userna
the differences between your Development Database and your Schema Model on disk and save this into an artifact (in temp folder) for later
https://documentation.red-gate.com/dso/redgate-change-control/terminology-reference/shadow-scripts-folder, this command will reset the sh
/dso/flyway-desktop-formerly-redgate-change-control/working-with-the-command-line-and-docker
-ServerInstance "staging01\sql2012" -Database "Staging" -Username "sa" -Password "P@ssw0rd" $test = New-DlmDatabaseConnection -ServerInst
/dlma2/using-sql-compare-options-with-dlm-automation-cmdlets
-ServerInstance your-server\sql2012 -Database WidgetStaging -Username sa -Password p@ssw0rd $productionState = New-DlmDatabaseConnection
/sr1/worked-examples/deploying-a-database-using-powershell-scripts
