With the last article (https://datalere.com/automating-datab…nning-roundhouse/) we walked through running a RoundhousE deployment for the first time to create the database and several database objects. Script naming importance was talked about to help maintain the correct execution order. The tables were empty so a second deployment was run with new scripts added to populate the tables. [...]
About Jack GraberJack Graber has worked with SQL Server for the past 15 years. He has worked with ETL, reporting, database development and supporting enterprise applications on SQL Server.
Now that we have a basic understanding of RoundhousE database deployment from the first two parts of this series let’s get to the good stuff. If you haven't read the first articles you might take some time to go back through them. Here are links to those first two. https://datalere.com/automating-database-deployment/ https://datalere.com/setting-up-the-r…ouse-environment/ This walkthrough will setup [...]
Remember from the introduction that RoundhousE is a command line driven database deployment engine. This article of the series will discuss the deployment flow and the RoundhousE environment, looking at the default behavior and how to modify it using command line switches. When a RoundhousE deployment is run the first step is a check to [...]
Database Deployment in DevOps One of the many obstacles to database development and DevOps is how to deploy databases consistently and how to automate the process. Database deployments have historically consisted of last minute treasure hunts to find or build scripts of the changes that have been made. Inevitably that leads to missed changes, no [...]