Comments
Sort by recent activity
David, Thanks for the quick reply, As long as all the features of Redgate Change Control reside within the same tool, I think it would be a greatly welcomed addition. I know my team and myself would have great interest in the product. Thanks for the information and we look forward to the release. Thanks! Scott / comments
David,Thanks for the quick reply, As long as all the features of Redgate Change Control reside within the same tool, I think it would be a greatly welcomed addition. I know my team and myself wou...
Now I'm wondering if I need to add the compare option to the Octopus deployment process. The compare option is saved with the repository, but the default options could be overriding the settings. On the other hand, the option does work for pre/post scripts without adding the compare option to the Octopus deploy process. I can see in the deploy artifacts that there is no BEGIN TRANSACTION in the pre/post scripts. / comments
Now I'm wondering if I need to add the compare option to the Octopus deployment process. The compare option is saved with the repository, but the default options could be overriding the settings. ...
I still get the error when a deployment tries to drop a memory optimized table unless it's stated in our post scripts. Even with "Don't use transactions in deployment script" selected. [image] [image] [image] [image]
WARNING: The error 'DDL statements ALTER, DROP and CREATE inside user transactions are not supported with memory
optimized tables.' occurred when executing the following SQL:
WARNING: DROP TABLE [dbo].[Test]
The database post script failed
The database update succeeded
NotSpecified: Applying update script failed: DDL statements ALTER, DROP and CREATE inside user transactions are not supported with memory optimized tables.
At C:\Octopus\Work\20200526160027-126559-269\Script.ps1:289 char:46
+ ... xportPath | Use-DatabaseReleaseArtifact -DeployTo $databaseConnection ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
at <ScriptBlock>, C:\Octopus\Work\20200526160027-126559-269\Script.ps1: line 289
at <ScriptBlock>, C:\Octopus\Work\20200526160027-126559-269\Bootstrap.Script.ps1: line 2799
at <ScriptBlock>, <No file>: line 1
at <ScriptBlock>, <No file>: line 1
Applying update script failed: DDL statements ALTER, DROP and CREATE inside user transactions are not supported with memory optimized tables.
The remote script failed with exit code 1
/ comments
I still get the error when a deployment tries to drop a memory optimized table unless it's stated in our post scripts. Even with "Don't use transactions in deployment script" selected.
WARNING: Th...
Thanks for the response. I may have misunderstood the scope of that option. I thought it was limited to the pre and post scripts sections only. I thought I had tested that option within the repository without pre/post scripts, but now I'm not sure it I tested that correctly. I will have to try that and see if it works. Thanks! / comments
Thanks for the response. I may have misunderstood the scope of that option. I thought it was limited to the pre and post scripts sections only. I thought I had tested that option within the repo...
I was able to get the process to work by doing this, but I also have to run custom scripts to drop memory objects out of our build server database and test database instances, since once they get created by our post scripts, the core repo deployment cannot remove these objects because they are within a transaction. Which then I've also created filters to ignore objects/schemas, but this is getting very complicated to do something as simple as creating a table. Now our developers have to remember to go and run the post script to create the memory tables on their local instance in order to test. / comments
I was able to get the process to work by doing this, but I also have to run custom scripts to drop memory objects out of our build server database and test database instances, since once they get c...
Yes, I have already disabled transactions in the pre/post scripts. The issue is that we have objects in our repository that reference these memory optimized tables to extract data after the ETL process, but they fail on deployment unless we disable IncludeDependencies which decreases our data/object integrity of the database. Which then we can remove the memory tables from the repository definition, but then our users do not get the objects installed on their local machine through source control unless they run the post scripts manually. / comments
Yes, I have already disabled transactions in the pre/post scripts. The issue is that we have objects in our repository that reference these memory optimized tables to extract data after the ETL pr...
If the memory optimized tables are included in our actual repository, the deployment fails with the error "DDL statements ALTER, DROP and CREATE inside user transactions are not supported with memory optimized tables." Which means we can't include them in the repository, just in a post scripts. / comments
If the memory optimized tables are included in our actual repository, the deployment fails with the error "DDL statements ALTER, DROP and CREATE inside user transactions are not supported with memo...
Sorry for taking so long to get back to this issue. The variable changes does work. Thanks! / comments
Sorry for taking so long to get back to this issue. The variable changes does work. Thanks!
I will test that out. Thank you! / comments
I will test that out. Thank you!