-ServerInstance "test01\sql2012" -Database "Test" -Username "sa" -Password "P@ssw0rd" $filter = "C:\Work\MyFilter.scpf" New-DatabaseRelea
"AdventureWorksIntegration" -Username "sa" -Password "P@ssw0rd" By assigning the output of New-DatabaseConnection to a variable, you can
/sca3/automating-database-changes/automated-deployments/setting-up-database-connections
with a default password of P@ssw0rd was instead created. Corrupt login SQL Compare displays this warning when the login for a user is not
" -Database "Staging" -Username "AutomationUser" -Password "P@ssw0rd" This example shows how to create a Database Connection object. The o
https://documentation.red-gate.com/fd/flyway-cli-and-api/commands/undo. What is the best strategy for dealing with hot fixes? You have a
to the live database after Version 1.2 was released, eg. using SQL Management Studio. This effectively created a new version of the schem
If you are monitoring PostgreSQL instances on Amazon RDS or Aurora clusters, then you can set up Redgate Monitor to authenticate via AWS I
/monitor14/enabling-aws-iam-postgresql-authentication-246972466.html
running the command line formatter. This argument is required. --path -p The file or directory to format. This argument is required. --cr
schema, and data) of SQL Backup .sqb files with a live database, and then synchronize the database with the backup file contents while ma
development at Redgate. It's designed to log performance data on live, running ASP.NET applications. The tool logs method calls as they h
/app9/release-notes-and-other-versions/ants-performance-profiler-7-0-release-notes
" -Database "Staging" $test = New-DlmDatabaseConnection -ServerInstance "test01\sql2014" -Database "Test" -Username "AutomationUser" -Pass
for SQL Toolbelt. Fixes Row-level security policy block predicates are now correctly registered from on-premise live databases SQL Compar
/sc13/release-notes-and-other-versions/sql-compare-13-0-release-notes
\sql2014" -Database "Staging" $test = New-DatabaseConnection -ServerInstance "test01\sql2014" -Database "Test" -Username "AutomationUser"
/sca4/reference/powershell-cmdlets/new-databasereleaseartifact
in the live application) and incrementing this new start-point by “1” for each key value to be replaced. At this point it is also worthwh
/dms7/data-masker-help/tech-tips/how-do-i-change-a-primary-key-value-and-all-associated-foreign-keys
, then type: p The suggestions box shows all relevant suggestions beginning with p : example1_2.gif SQL Prompt always places the most cont
, then type: p The suggestions box shows all relevant suggestions beginning with p : example1_2.gif SQL Prompt always places the most cont
and off for projects created in earlier versions of Schema Compare Populating from scripts progress messages now match those for live pop
/sco6/schema-compare-for-oracle-3-0-release-notes-148079350.html
that are not relevant when deploying to a scripts folder Schema compare engine updates Features Performance improvement as live database
/sco6/schema-compare-for-oracle-3-1-release-notes-148079348.html
be detected as different when comparing a live database and a scripts folder. Version 5.7.17 - July 21st, 2021 Fixes OC-1323: Procedures
/sco6/schema-compare-for-oracle-5-7-release-notes-148079330.html
development at Redgate. It's designed to log performance data on live, running ASP.NET applications. The tool logs method calls as they h
/app10/release-notes-and-other-versions/ants-performance-profiler-7-0-release-notes
"AdventureWorksIntegration" -Username "sa" -Password "P@ssw0rd" By assigning the output of New-DatabaseConnection to a variable, you can
/sca4/deploying-database-changes/automated-deployments/setting-up-database-connections
:\Work\scripts\" $test = New-DlmDatabaseConnection -ServerInstance "test01\sql2012" -Database "Test" -Username "sa" -Password "P@ssw0rd" $
development at Redgate. It's designed to log performance data on live, running ASP.NET applications. The tool logs method calls as they h
/app11/release-notes-and-other-versions/ants-performance-profiler-7-0-release-notes
can generate deployment scripts with migrations using the following source/target types: Source: Scripts folder Source control Target: Li
of type BINARY can now be registered from live databases.
/soc6/release-notes-and-other-versions/sql-source-control-5-2-release-notes