3 ms·
Give the new proc a different name (e.g. append a version number). On the n+1 deployment, clean up the old proc.
by platz 10y ago
Give the new proc a different name (e.g. append a version number). On the n+1 deployment, clean up the old proc.
- Nullabillity 10y agoAnd so you've reinvented the version control system on top of your deployment system, on top of your version control system. That also sounds fun if you use the proc from more than one location...
- platz 10y agoZero downtime deployment with stored procedures should not be confused with "version control". It's not a version control scheme; once deployed the procs are never updated.
- brightball 10y agoYea, I suppose backwards compatibility is really the best policy there. If a proc is going to be updated to be more efficient it's one thing. If it's going to change what it does then we just need a new proc.
- platz 10y agoYep. (if there are schema, changes too, zero downtime & backward compatability is difficult to pull off, but thats a chore for any strategy )