DB deltas in multi-develop environ

I'm looking for some advice on how your organization handles DB changes in an environment that includes a number of concurrent development projects. To date, the development projects have been isolated from each other in terms of schema changes. When a project went on-line all we had to do was put out the new tables on the production servers and we were in business. We're now faced with several projects which need to be in-process and these projects will require changes in a number of global tables. These global tables are used by projects already out in the field. It is expected that not all of the table changes will be known at the same time and we could face a situation where one project needs to move on to test/production and once there changes for another project would become evident in some or all of the global tables. What/how do you handle situations like this? I am also trying to keep the schemas controlled under SCCS. I have some ideas but wuold like to talk with a few others. BTW, we're dealing with about 3 development servers and 135 production servers in 5 western states so simplicity is an important factor. Please respond via e-mail and my thanks in advance. Carlton -- _____________________________________________________________________ Carlton Doe DBA Resources, Inc. Salt Lake City, UT