Activity overview
Latest activity by SteffenCHBeck
@David Atkinson, for regular deployments to staging and production we use deployment scripts generated by SQLCompare. Deployment Scripts are executed by liquibase containers in Kubernetes. (We did not check if switching to free flyway version will have advantages. Liquibase is company standard, used by other teams which are not using Toolbelt&SQLCompare, too) For development of existing Procs/Views we open file from scripts folder, modify and execute on development instance. Thus Procs,Views,... need to have CREATE OR ALTER. New Procs/Views often are created in development instance and later are generated to scripts folder with SQLCompare Sometimes it's necessary to create existing scripts back to scripts folder, for instance because of tiny differences in the database representation. / comments
@David Atkinson,for regular deployments to staging and production we use deployment scripts generated by SQLCompare. Deployment Scripts are executed by liquibase containers in Kubernetes. (We did n...
@David Atkinson I'm creating a scripts folder from database (with Version 15.3.6.25729) / comments
@David Atkinson I'm creating a scripts folder from database (with Version 15.3.6.25729)
@David Atkinson, yes I can confirm "Add CREATE OR ALTER for rerunnable scripts where possible" is checked / comments
@David Atkinson, yes I can confirm "Add CREATE OR ALTER for rerunnable scripts where possible" is checked
Is there a possibility to vote for this feature? Right now I wanted to regenerate some scripts because SQLCompare shows differences - for instance because of trailing semicolon after END of Stored Procedure. Regenerating script with SQL Compare removes existing "OR ALTER" statements even if there was no difference before. Code Reviewers ask why I removed this. / comments
Is there a possibility to vote for this feature?Right now I wanted to regenerate some scripts because SQLCompare shows differences - for instance because of trailing semicolon after END of Stored P...