In part 2 of my series on dab, we'll run dab in an Azure Container Instance and wire it up to create an API on top of an Azure SQL Database.
Well this sounds scary, CI\CD pipelines and potential data loss are two phrases we do not want next to each other. But stick with me, in some cases we want to deploy database changes that might cause data loss.
Let's test out the Data API Builder (dab) to create API endpoints for a local SQL Server database running in a container.
Recently I was reading the docs for `Backup-DbaDatabase` and found a parameter I didn't realise existed, but is so useful when you want to automate backups, but keep control of the file names.
Have you ever had to do a little switch-a-roo on a table? Renaming the current one to append _old, so you can create a new one in it's place? Have you ever forgotten to go back and clear those up? Well, if so, this short blog is for you!
