Comments
Sort by recent activity
Correct, you only need the plugins from the marketplace. / comments
Correct, you only need the plugins from the marketplace.
There is a PowerShell gallery package for SQL Change Automation (https://www.powershellgallery.com/packages/SqlChangeAutomation/) this can be installed for just the current user. The plugins will install from there, meaning VSTS hosted agents can download and use the software. In short yes you can use hosted agents, we pull down the package as part of the build/release. / comments
There is a PowerShell gallery package for SQL Change Automation (https://www.powershellgallery.com/packages/SqlChangeAutomation/) this can be installed for just the current user. The plugins will i...
That's great to hear. Hope it all works for you now. / comments
That's great to hear. Hope it all works for you now.
As it stands no. I was remembering this from an older version of Octopus. Aplogies. / comments
As it stands no. I was remembering this from an older version of Octopus.Aplogies.
Hi Anthony, Sorry about that. We are currently working on a fix to the step templates that will address this issue. In the mean time you can modify the step template by going to Library > Step Templates and selecting our template for edit. Then replace the following line $dlmAutomationModule = Get-Module -ListAvailable -Name DLMAutomationwith $dlmAutomationModule = Get-Module -ListAvailable -Name SQLChangeAutomation / comments
Hi Anthony,Sorry about that. We are currently working on a fix to the step templates that will address this issue. In the mean time you can modify the step template by going to Library > Step Templ...
Hi, This is not currently supported in SQL Source Control. We have a uservoice request for this feature: https://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/18580312-require-a-commit-message-for-git please feel free to vote for it. / comments
Hi,This is not currently supported in SQL Source Control. We have a uservoice request for this feature: https://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/18580312-require-a-...
We have done the work and are in the process of releasing the fix to the Octopus Community step template library. You can track the progress here https://github.com/OctopusDeploy/Library/pull/700 / comments
We have done the work and are in the process of releasing the fix to the Octopus Community step template library. You can track the progress here https://github.com/OctopusDeploy/Library/pull/700
Hi, We have some tutorials listed in our help docs: https://documentation.red-gate.com/dlma2/tutorials In particular https://documentation.red-gate.com/dlma2/tutorials/walkthrough-set-up-continuous-integration-and-release-management (this uses TeamCity and Octopus Deploy, other CI/CD tools are covered in https://documentation.red-gate.com/dlma2/tutorials/using-the-dlm-automation-add-ons) / comments
Hi,We have some tutorials listed in our help docs: https://documentation.red-gate.com/dlma2/tutorialsIn particular https://documentation.red-gate.com/dlma2/tutorials/walkthrough-set-up-continuous-i...
This has been fixed in a recent frequent update to SQL Source Control. You can find details on how to enable frequent updates here https://documentation.red-gate.com/soc6/installing-licensing-and-updating/update/configuring-frequent-updates / comments
This has been fixed in a recent frequent update to SQL Source Control. You can find details on how to enable frequent updates here https://documentation.red-gate.com/soc6/installing-licensing-and-u...
Your syntax looks correct. To help work out what is going wrong could you add -Debug -Verbose to your call
Sync-DlmDatabaseSchema -Source $scriptsFolder -Target $ci -AbortOnWarningLevel None -IgnoreAdditional -Verbose -Debug
And then copy paste the following two lines:
VERBOSE: Calling: C:\Program Files (x86)\Red Gate\DLM Automation 2\SC\SQLCompare.exe /options:ConsiderNextFilegroupInPartitionSchemes,DecryptPost2kEncryptedObjects,DoNotOutputCommentHeader,ForceColumnOrder,IgnoreCertificatesAndCryptoKeys,IgnoreDatabaseAndServerName,IgnoreTSQLT,IgnoreUserProperties,IgnoreUsersPermissionsAndRoleMemberships,IgnoreWhiteSpace,IgnoreWithElementOrder,IncludeDependencies,NoDeploymentLogging,ThrowOnFileParseFailed,UseCompatibilityLevel /transactionIsolationLevel:SERIALIZABLE /exclude:Additional "/scriptFile:C:\Users\Peter.Gerrard\AppData\Local\Temp\DLM Automation\xfjrl2uk.sql" /showWarnings /include:Identical "/report:C:\Users\Peter.Gerrard\AppData\Local\Temp\DLM Automation\0gmntwax.xml" /reportType:Xml /assertidentical /force /OutputWidth:1024 /server1:.\sql2016 /database1:northwind /server2:.\sql2016 /database2:northwind /out:"C:\Users\Peter.Gerrard\AppData\Local\Temp\DLM Automation\b0ocjlc0.log"
DEBUG: SQL Compare Command Line V13.1.8.5471
/ comments
Your syntax looks correct. To help work out what is going wrong could you add -Debug -Verbose to your call
Sync-DlmDatabaseSchema -Source $scriptsFolder -Target $ci -AbortOnWarningLevel None -Ignor...