I meant the concept of verson control for DB's.Revision control for DBs is fine. We use it ourselves. Via files. And then when it came time for you to describe why doing it in the database was better, you said "You Win!"
No. Hiring DBA's is a "divide and conquer" strategy.Because managing a database takes more knowledge and effort than managing a source code control repository, as you have apparently conceded by failing to respond to my questions about adding a new column. Additionally, adding an extra database involves even more work, unlike using a single source code repository.
However you label it, it is not more effort than doing the same in a class.Nope, no back-tracking here, Bryce. I've already established and you've already conceded that maintaining control tables [link|/forums/render/content/show?contentid=157245|is more work].
Concession noted for posterity: reporting on code is useless for the sales/marketing people given specs and documentation.