= New-DlmDatabaseConnection -ServerInstance "prod01\sql2014" -Database "Production" -Username "sa" -Password "P@ssw0rd" Test-DlmDatabaseC
", "-U", "MyUser", "-P", "MyPassword", "-d", "MyDatabase", "-Q", "SELECT 1"] interval: 10s retries: 20 The build step is here being contro
Server user name to use to log in if you are using SQL Server authentication. -P -P <SQL_Server_password> Specifies the password to use t
" -Username "sa" -Password "p@ssw0rd" $DB2 = New-DlmDatabaseConnection -ServerInstance "your-server\sql2014" -Database "WidgetProduction"
/dlma1/get-started/get-started-with-the-dlm-automation-cmdlets/deployment
forcecolumnorder f forwardslash s defineoff d blanklineson b excludetargetschema e detectcolumnrenames r purgedroptable p suppressalterco
forcecolumnorder f forwardslash s defineoff d blanklineson b excludetargetschema e detectcolumnrenames r purgedroptable p suppressalterco
" -Database "Staging" -Username "sa" -Password "P@ssw0rd" $package = "C:\NuGetFeed\database.nupkg" $update = New-DlmDatabaseRelease -Sourc
"sa" -Password "P@ssw0rd" Sync-DlmDatabaseSchema -Source $scriptsFolder -Target $test This example show how to update a test database to
> Specifies the SQL Server user name to use to log in if you are using SQL Server authentication. -P -P <SQL_Server_password> Specifies th
, and crossschemapermissions) Value Option scriptheader h forcecolumnorder f forwardslash s defineoff d blanklineson b excludetargetschema
nmap -p {port} --script ssl-cert {address} openssl cat /dev/null | openssl s_client -showcerts {address}:{port} 2>/dev/null | openssl x50
-ServerInstance "your-server\sql2014" -Database "WidgetStaging" -Username "sa" -Password "p@ssw0rd" $DB2 = New-DlmDatabaseConnection -Ser
/dlma2/get-started/get-started-with-the-dlm-automation-cmdlets/deployment
> Specifies the SQL Server user name to use to log in if you are using SQL Server authentication. -P -P <SQL_Server_password> Specifies th
/password:P@ssw0rd /password:<password> Alias: /p The password for connecting to the server. You must also provide a username. If you don
> Specifies the SQL Server user name to use to log in if you are using SQL Server authentication. -P -P <SQL_Server_password> Specifies th
-SQL "RESTORE DATABASE master FROM DISK = 'C:\Backups\master 20070101.sqb'" -I Instance2 If you are using SQL Server authentication, use
\sql2014" -Database "Test" -Username "AutomationUser" -Password "P@ssw0rd" Sync-DlmDatabaseSchema -Source $scriptsFolder -Target $test Thi
/password:P@ssw0rd /password:<password> Alias: /p The password for connecting to the server. You must also provide a username. If you don
, and crossschemapermissions) Value Option scriptheader h forcecolumnorder f forwardslash s defineoff d blanklineson b excludetargetschema
-------------------------- Update-ClassificationInLiveDatabase -instanceName "sqlserver\sql2016" -databaseName "WideWorldImporters" -user
---------- $connection = New-DlmDatabaseConnection -ServerInstance "prod01\sql2014" -Database "Production" -Username "sa" -Password "P@ss
Better handling of renaming assemblies that are merged Fixed bugs in pruning related p/Invoke calls Major bugs in highest obfuscation lev
/sa6/release-notes-and-other-versions/smartassembly-5-0-release-notes
. The option must be preceded by a minus sign. $staging = New-DatabaseConnection -ServerInstance "staging01\sql2012" -Database "Staging" -
" -Password "P@ssw0rd" By assigning the output of New-DlmDatabaseConnection to a variable, you can reuse this as the input for another cmd
"Installing SmartAssembly from $msiPath into $saInstallLocation" $p = Start-Process -FilePath msiexec -Args "/qn /i `"$msiPath`" INSTALLD
/sa8/building-your-assembly/using-smartassembly-with-azure-pipelines/example-of-azure-pipelines-yml
