rollout of DB changes to production...

From: Richard Huntley <rhuntley_at_mindleaders.com>
Date: Thu, 07 Jun 2001 12:01:19 -0700
Message-ID: <F001.00320ACD.20010607103748@fatcity.com>

I'm just wondering if the best way to handle a rollback of added columns is to alter the table to mark the column as unused and then drop the unused columns via ALTER TABLE t1 DROP UNUSED COLUMNS; or would the ideal thing be to export the table(s) before adding the columns and then reimport, although that could get very sticky since I'd be dealing with the whole table and associated constraints instead of just the columns I'm trying to remove. I basically want to have both a rollout and a rollback script for an upcoming rather large move to production. Your input would be greatly appreciated.

TIA, Richard Huntley
E-mail: rhuntley_at_mindleaders.com

--

Please see the official ORACLE-L FAQ: http://www.orafaq.com
--

Author: Richard Huntley
  INET: rhuntley_at_mindleaders.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Thu Jun 07 2001 - 14:01:19 CDT