Activity overview
Latest activity by robrich
The way I've solved this is to check in a tools directory with all the exe's I need, then call them from scripts called from GitHub Actions. Now that containers exist for all the tools, one could use docker commands from Actions. This isn't quite as clean as the action commands you can grab from GitHub's marketplace, but it isn't that difficult to build your own if you really want it. Derive from Redgate's container, add an action.yml and README.md, and if you want to go full-circle, publish to the marketplace. See also https://docs.github.com/en/actions/creating-actions/creating-a-docker-container-action and https://hub.docker.com/u/redgate / comments
The way I've solved this is to check in a tools directory with all the exe's I need, then call them from scripts called from GitHub Actions. Now that containers exist for all the tools, one could ...
How has SQL Change Automation helped me? DevOps has made building and deploying apps a breeze. But what about the database? Should we continue RDPing into the server and manually running scripts? Of course not! SQL Change Automation is that magic piece that unlocks DevOps for databases. Hook it up to developers and we can now communicate both app and database changes in one git push. Hook it up to CI and we can now prove there aren't any syntax or logic errors in our SQL. Hook it up to tSQLt or SQL Test and we can now unit test our sql functions just like we unit test our code functions. And finally hook it up to the deployment databases in all environments, lock everyone out of those databases, and we now have confidence that if it ran in pre-prod it'll run great in prod too. After all, we practiced the production deployment with every DevOps build since the change was introduced. Just saying, DevOps with Databases is completely a thing, and SQL Change Automation is the elegantly simple way to do it. / comments
How has SQL Change Automation helped me? DevOps has made building and deploying apps a breeze. But what about the database? Should we continue RDPing into the server and manually running scripts...
SQL Change Automation from GitHub Actions?
I'm at MVP Summit, and have a question. Do we have a story for SQL Change Automation on GitHub Actions in the same way we have a story in similar build & release tools like Azure DevOps pipelines, ...
SQL Monitor to Azure SQL Database?
Can I connect SQL Monitor to an Azure SQL Database? Gut feel is this isn't the right tool for the job. What should I use instead?