July 8, 2013
I’ve been recently working with a couple of customers who were dropping database columns from their schema on Oracle, and the drops were taking a long time to complete. In one instance, the customer estimated it would take 50 hours to drop a bunch of columns from their contact table. In another, a customer observed that dropping two columns from table_site_part took over two hours. Dropping 3 columns from table_contact took over 1 hour. These long execution times can disrupt normal operations – especially those environments with limited maintenance windows. Dovetail’s schema editing tool (Schema Editor) and Amdocs schema editing tools (ddcomp, SchemaManager) all do the same basic operations when it comes to dropping columns. Basically they all do this: ALTER TABLE table_name DROP COLUMN column_name; There’s a better way. Set Unused On large tables the process of physically…
SchemaEditor improvements when dropping columns on Oracle
July 8, 2013
I’ve been recently working with a couple of customers who were dropping database columns from their schema on Oracle, and the drops were taking a long time to complete. In one instance, the customer estimated it would take 50 hours to drop a bunch of columns from their contact table. In another, a customer observed that dropping two columns from table_site_part took over two hours. Dropping 3 columns from table_contact took over 1 hour. These long execution times can disrupt normal operations – especially those environments with limited maintenance windows. Dovetail’s schema editing tool (Schema Editor) and Amdocs schema editing tools (ddcomp, SchemaManager) all do the same basic operations when it comes to dropping columns. Basically they all do this: ALTER TABLE table_name DROP COLUMN column_name; There’s a better way. Set Unused On large tables the process of physically…