After reading:
Is online db change possible?
Has anyone come up with an ingenious way (in Progress - not SQL or ODBC etc.) to get around this?
Our IT Director has proposed the following:
Create a copy of the LIVE db - in both schema and data. We'll call the new copy SchemaChanger.db. Have the developers develop against SchemaChanger.db and make their necessary db modifications. Then have a nightly process kick off (when all the users are snug in their beds) that automatically updates the schema of LIVE with the schema of SchemaChanger - not data, just the schema.
You could also use SchemaChanger as a TEST db and only update data FROM LIVE to TEST as needed.
Has anyone tried this approach or has a better one in place?
-dk-
Is online db change possible?
Has anyone come up with an ingenious way (in Progress - not SQL or ODBC etc.) to get around this?
Our IT Director has proposed the following:
Create a copy of the LIVE db - in both schema and data. We'll call the new copy SchemaChanger.db. Have the developers develop against SchemaChanger.db and make their necessary db modifications. Then have a nightly process kick off (when all the users are snug in their beds) that automatically updates the schema of LIVE with the schema of SchemaChanger - not data, just the schema.
You could also use SchemaChanger as a TEST db and only update data FROM LIVE to TEST as needed.
Has anyone tried this approach or has a better one in place?
-dk-