How to Implement CI/CD in Azure Data Factory (ADF)
Learn how you can use CI/CD with your ADF Pipelines and Azure DevOps using ARM templates.
2023-03-10
13,664 reads
Learn how you can use CI/CD with your ADF Pipelines and Azure DevOps using ARM templates.
2023-03-10
13,664 reads
Flyway Teams baseline migration scripts are a simple and fast way to deploy new copies of a database, at a specific version, for testing work, or to create a new branch during development.
2021-11-17
Grant Fritchey discusses the relationship between microservices architecture and database deployment and how these two important pieces of the DevOps puzzle, can work together, or against each other in the future.
2021-07-28
How Redgate Deploy will help you ensure that databases and applications can grow and develop in step, and to implement a workflow for delivery of database changes that is resilient, repeatable, fast and visible.
2021-07-19
Compare the schemas of two SQL Server databases using SQL Compare command line then quickly produce a diff report showing you immediately which tables, views and functions have changed.
2021-07-16
How to exploit the branching and merging capabilities of Git for scaling up team-based development, when doing Flyway migrations.
2021-06-18
The cloud migration tools and processes that will help you move a database to the cloud, from planning, implementation and validation through to extending existing development and deployment processes to the new cloud platform.
2021-06-14
How to write idempotent DDL scripts that Flyway can run several times on a database, such as after a hotfix has already been applied directly to the production database, without causing errors.
2021-05-21
How to extend the range of SQL code analysis, during database development, to include dynamic analysis of the database metadata. This will allow regular checks for problems with the design of your tables and indexes ("table smells") that can affect database performance and data integrity.
2021-05-10
How to detect database drift prior to running a database migration, so that you can be certain that a database hasn't been subject to any 'uncontrolled' changes that could affect the migration or result in untested changes being deployed to production.
2021-04-28
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers