Steve Jones - SSC Editor (1/26/2015)
Eric M Russell (1/26/2015)
So, deploying a new procedure, table, or column days or weeks before the associated application change is deployed? Yes, that happens all the time in my universe where the database development and application development teams are seperate. The database comes before the application, both for the initial deployment and change request deployments.Good to hear. Don't hear many people doing it.
Well, they're just making their lives difficult for no reason. If the application and database changes are deployed in tandem, and the application deployment has to be rolled back, then does that mean the related database deployment has to be rolled back too? I don't want to do that unless it's absolutely necessary. The way I see it, the database, ETL, and application(s) are seperate systems that communicate using a contract. The goal of the database developer is not to break that contract, which shouldn't occur simply because a new procedure or column has been added.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho