Comments
Sort by recent activity
This work should be complete now. Run Check for Updates from the tool or update via the Toolbelt installer. / comments
This work should be complete now. Run Check for Updates from the tool or update via the Toolbelt installer.
We will be adding SSMS 20 support to SQL Source Control. However, it might be worth considering switching to Flyway as this is the next-gen product. If you're using git, Flyway Desktop has much improved git support built in, for example. / comments
We will be adding SSMS 20 support to SQL Source Control. However, it might be worth considering switching to Flyway as this is the next-gen product. If you're using git, Flyway Desktop has much imp...
This is being assessed right now, so I can't provide an ETA just yet. / comments
This is being assessed right now, so I can't provide an ETA just yet.
If by "suitable for commercial projects" you mean if you can legally use it, then it's "yes". Flyway Community Edition is designated as 'freeware' (as per Redgate's software editions page). Freeware is further defined in the Subscription EULA License which can be found here. / comments
If by "suitable for commercial projects" you mean if you can legally use it, then it's "yes".Flyway Community Edition is designated as 'freeware' (as per Redgate's software editions page). Freeware...
By "develop using the schema model" I mean that developers only save changes to the schema model, commit/push these to the branch, and other developers use apply to database to sync their database with other's changes. Avoid using migration scripts until there's a level of confidence that they're ready. Migration scripts can be created in the feature branch. That's entirely optional. If the developer who has made the changes is confident to generate the migration scripts, I'd suggest the right time would be in the feature branch, before merging. If they're not created at this stage, then the migration scripts can be created after the (schema model) changes are merged to the dev branch. This would be appropriate if a different developer is charged with creating the migration scripts. / comments
By "develop using the schema model" I mean that developers only save changes to the schema model, commit/push these to the branch, and other developers use apply to database to sync their database ...
I would strongly recommend using the same scripts in all environments. If you have migration scripts in dev that need to be rolled up, best to delete them, recreate your development database and generate a new script. An approach is to avoid creating migration scripts in development, as these are likely to need to be deleted and recreated after the "back and forth". Just develop using the schema model, and only when you're confident that the changes need to be promoted to higher environments do you generate the migrations. / comments
I would strongly recommend using the same scripts in all environments. If you have migration scripts in dev that need to be rolled up, best to delete them, recreate your development database and ge...
Which edition of Flyway do you use (Community, Teams or Enterprise), and what database are you using it with? This will help me suggest options. / comments
Which edition of Flyway do you use (Community, Teams or Enterprise), and what database are you using it with? This will help me suggest options.
I'm not sure I understand why each environment needs to have a different set of migration scripts. Ideally you want to aim for the same migration scripts being used to update all environments as knowing the same migration scripts have been exercised in lower environments will provide you with maximum confidence that the eventual deployment to production will run as expected. / comments
I'm not sure I understand why each environment needs to have a different set of migration scripts. Ideally you want to aim for the same migration scripts being used to update all environments as kn...
Hi, What do you mean by "production migration scripts"? Are ther scripts that should run on all environments, and some scripts that should only run on specific environments? If so, can you give an example of what might be applied to production but shouldn't be applied to Dev or QA? / comments
Hi, What do you mean by "production migration scripts"? Are ther scripts that should run on all environments, and some scripts that should only run on specific environments? If so, can you give an ...
Flyway itself is solely concerned with versioning and deploying database changes. Redgate does, however, offer a monitoring solution and a test data management solution, both of which complements Flyway. / comments
Flyway itself is solely concerned with versioning and deploying database changes. Redgate does, however, offer a monitoring solution and a test data management solution, both of which complements F...