Re: Parsing the spool file.....

The configuration approach you mention is very sensible. Normally under development, we create table, grant/revoke and other amazing feats on ah doc basis for fast turnaround time. How do we implement and propagate changes in an effective and efficient manner to our production environment?

For me, I would develop a script and run it on our test enviornment. If there is any error, fix it, restore the system and rerun until no error is obtained.This would not only verify the script but force one to test the backup and restore procedures as well. Nowadays, since most tools are going to GUI-based, developing script is not that easy. However, we would adopt the similar approach, ie, document every step with response and capture every damned screen shot and run the document several times on our testing environment.

Then when we apply to the production, we would just follow the procedure developed in the test environment and have as little unexpected surprise as possible.

I would like to know if there is better alternative than this "dump ass approach". Received on Thu Oct 05 2006 - 14:08:07 CDT