![multiple select and editing with redgate sql toolbelt tips and tricks multiple select and editing with redgate sql toolbelt tips and tricks](https://www.red-gate.com/wp-content/uploads/2018/12/word-image-5.png)
![multiple select and editing with redgate sql toolbelt tips and tricks multiple select and editing with redgate sql toolbelt tips and tricks](https://dataedo.com/asset/img/blog/redgate_sql_doc_editor.png)
The build DB would have to be created from the clone/backup/other every time instead of simply cleaning the schema down.To get this stage to work though, you would need to do a couple of things differently: Instead of running EVERY migration we’ve ever written, which could take a while for a large team, we run only the latest migrations to check that they would deploy happily to the Production target. Ready to go, ready to test, ready to give us the best possible insight into our changes. and these can all just be a stage in the YAML file before invoking Flyway but the point is, if we use an existing copy of our Prod database from some source or another, it will have 2 things we really care about: Of course there are lots of other options, like restoring a backup or spinning up a container etc. Of course if we hold any sensitive PII/PHI then we should ensure that is protected first! There’s a few methods to achieve this – my personal favorite would be to use a SQL Clone, spin that up on a build VM rather than using an Azure SQL DB, and we can have all the data in an instant. Maybe, maybe not depending on what is in there. What we have in Production is what will have these changes deployed to it… eventually! So shouldn’t we just test against that? Well.
MULTIPLE SELECT AND EDITING WITH REDGATE SQL TOOLBELT TIPS AND TRICKS INSTALL
There are numerous ways to invoke tools and applications and fortunately good CI/CD tools like Azure DevOps offer multiple ways to, for instance, run PowerShell or CLI steps from within the pipeline – so we could easily invoke SQL Data Generator on a VM or physical machine we have an Azure DevOps agent on – but this thinking also opens up the possibility of using something like Chocolatey to dynamically install the software on the Azure DevOps hosted pool VM during build (for the Redgate tools at the moment I suppose you’d need a Windows VM). Many of them also have a command line or PowerShell module that we can use to easily invoke them against a target, especially if that target is going to be persistent like my Flyway Azure SQL Build DBs!īecause I have access to it and because I’m using essentially SQL Server DBs, I could easily use Redgate SQL Data Generator – but to get the data you need you could use anything from DBATools Data Generation (also SQL Server) to FillDB for MySQL (which looks awesome and you could easily use this for Step 1 above too!) There are SO MANY technologies out on the inter-webs for generating data. A bonus win for this step of course, is that where Devs have their own Flyway config files locally for their development databases they could also overwrite this behavior and point the testing and/or data scripts at their own database so they have some seed data to work with too! 2 – Add a data generation step to the pipeline