' user = 'SA' password = 'mySecretPwd' connectRetries = 10 initSql = 'SET ROLE \'myuser\'' schemas = ['schema1', 'schema2', 'schema3'] tab
flyway.driver=org.hsqldb.jdbcDriver flyway.url=jdbc:hsqldb:file:/db/flyway_sample flyway.user=SA flyway.password=mySecretPwd flyway.conne
>jdbc:hsqldb:file:${project.build.directory}/db/flyway_sample;shutdown=true</url> <user>SA</user> <password>mySecretPwd</password> <connec
> <user>SA</user> <password>mySecretPwd</password> <connectRetries>10</connectRetries> <initSql>SET ROLE 'myuser'</initSql> <schemas> <sch
of Hosted Storage from the UI Fixes SB-4756: {SA} OverflowException @ DataConvert.ToString(...) SB-5174: Clickable reminder actions no lo
/sbu10/release-notes-and-other-versions/sql-backup-pro-8-4-release-notes
\sql2014" -Database "Test" -Username "sa" -Password "P@ssw0rd" New-DlmDatabaseRelease -Source $test -Target $staging This example show how
. /temporaryDatabaseUserName=sa If you don't specify this switch, Windows authentication is used by default. /temporaryDatabasePassword (o
} } class MyPlugin : IPlugin { static MyPlugin() { //ensure that sa initialization is executed Program.Main(); } //your code here... } Wh
} } class MyPlugin : IPlugin { static MyPlugin() { //ensure that sa initialization is executed Program.Main(); } //your code here... } Wh
"sa" -Password "P@ssw0rd" By assigning the output of New-DlmDatabaseConnection to a variable, you can reuse this as the input for another
/dlma1/get-started/get-started-with-the-dlm-automation-cmdlets/setting-up-database-connections
-ServerInstance "test01\sql2012" -Database "Test" -Username "sa" -Password "P@ssw0rd" $filter = "C:\Work\MyFilter.scpf" New-DlmDatabaseRe
/dlma1/using-sql-compare-filters-with-dlm-automation-cmdlets
unprotected builds. If you have multiple projects Ensure that your SA project file is stored in the $(SolutionDir)\Build\ folder. It must
/sa6/building-your-assembly/using-smartassembly-with-clickonce-and-msi
SQL Compare and Data Compare make use of the built-in authentication mechanisms provided by Windows and are therefore limited to the Acti
SQL Compare and Data Compare make use of the built-in authentication mechanisms provided by Windows and are therefore limited to the Acti
SQL Compare and Data Compare make use of the built-in authentication mechanisms provided by Windows and are therefore limited to the Activ
but recommended.) For example: EXECUTE master..sp_addextendedproc sqbsetlogin, 'xp_sqlbackup.dll' EXECUTE master..sqbsetlogin 'sa', 'newp
/sbu6/errors-and-warnings/sql-server-errors/sql-server-error-18456-login-failed-for-user
to add the authentication details, for example: SQLBackupC.exe -SQL "RESTORE DATABASE master FROM DISK='C:\Backups\master 20070101.sqb'"
SQL Compare and Data Compare make use of the built-in authentication mechanisms provided by Windows and are therefore limited to the Acti
information, see Visual Studio Deployment Projects include unprotected builds. If you have multiple projects Ensure that your SA project
/sa8/building-your-assembly/using-smartassembly-with-clickonce-and-msi
information, see Visual Studio Deployment Projects include unprotected builds. If you have multiple projects Ensure that your SA project
/sa7/building-your-assembly/using-smartassembly-with-clickonce-and-msi
. SmartAssembly is run automatically, using the settings in your SmartAssembly project file. SA-2415
/sa7/building-your-assembly/using-smartassembly-with-msbuild/manual-integration
= 'org.hsqldb.jdbcDriver' url = 'jdbc:hsqldb:file:/db/flyway_sample;shutdown=true' user = 'SA' password = 'mySecretPwd' connectRetries =
. Sample configuration flyway { driver = 'org.hsqldb.jdbcDriver' url = 'jdbc:hsqldb:file:/db/flyway_sample;shutdown=true' user = 'SA' pass
configuration parameters. Sample configuration flyway.driver=org.hsqldb.jdbcDriver flyway.url=jdbc:hsqldb:file:/db/flyway_sample flyway.u
configuration flyway.driver=org.hsqldb.jdbcDriver flyway.url=jdbc:hsqldb:file:/db/flyway_sample flyway.user=SA flyway.password=mySecretPw
