Table Updates as Part of CM
Just out of curiousity, how do some of you handle table updates as part of the Configuration Management or even the Change Management Process? Generally, table updates don't affect the way the system is designed to work from a code aspect, but it could affect the outcome based on what code is executed based on the table data.
Do you test or require that table updates be tested before production?
Re: Table Updates as Part of CM
Perhaps I don't understand the context of your table changes. We develop COTS database products so there is nothing more critical than a table change. If it's a key change, we typically test all software that accesses the table. Do you mean something entirely different by 'table changes'?