Comments
Sort by recent activity
@Andrea_Angella thanks for the info, it was very helpful! / comments
@Andrea_Angella thanks for the info, it was very helpful!
Fixed by creating a custom step template and using:
New-OctopusArtifact "$exportPath\Reports\Changes.html" -Name "$DLMAutomationDatabaseName-Changes.html"
New-OctopusArtifact "$exportPath\Reports\Warnings.xml" -Name "$DLMAutomationDatabaseName-Warnings.xml"
New-OctopusArtifact "$exportPath\Update.sql" -Name "$DLMAutomationDatabaseName-Update.sql" / comments
Fixed by creating a custom step template and using:
New-OctopusArtifact "$exportPath\Reports\Changes.html" -Name "$DLMAutomationDatabaseName-Changes.html"
New-OctopusArtifact "$exportPath\Reports\W...
Rob,
I have another error, let me know if I should create a new post please?
[16:30:42][Step 1/2] "Latin1_General_CI_AS" in the equal to operation.
[16:30:42][Step 1/2] Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to
[16:30:42][Step 1/2] operation.' occurred when executing the following SQL:
I searched the code and there is no place where Latin1_General_CI_AS is set. The default on the database is "SQL_Latin1_General_CP1_CI_AS"
Any idea on how to fix this?
If I were to publish to a brand new database via Visual Studio it publishes fine.
Thank you!
UPDATE: I was able to get passed the error using the IgnoreCollations SQL Compare option / comments
Rob,
I have another error, let me know if I should create a new post please?
[16:30:42][Step 1/2] "Latin1_General_CI_AS" in the equal to operation.
[16:30:42][Step 1/2] Cannot resolve the collation...
Hello Robert,
This works! Thank you. / comments
Hello Robert,
This works! Thank you.