4 ms·

They mean version control here. I've worked at places where the schemas and stored procedures were not tracked anywhere - only the latest version existed in the

They mean version control here. I've worked at places where the schemas and stored procedures were not tracked anywhere - only the latest version existed in the database itself. Change control was a disaster. I've worked at places that threw scripts into a folder somewhere in a project, so that it would at least have history. Again, change control was a disaster. If you're not using a change control tool of some sort specifically for databases, and using it and only it to manage all changes, it's going to be a disaster.

usrbinbash 5y ago
Of course, but this also applies to all code. I still remember the time when it was deemed normal, or at least common, to email around diffs and patches in a dev team, or upload everything to the "code server" in little directories with iso-timestamps as names. Not taking care of code properly, aka. in a VCS, is a disaster, no matter if its C, SQL or utility bash-scripts.