Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Tue, 03 Apr 2012 @ 09:28:20 GMT

  <Prev Next>   <<First <Prev

Subj:   Re: Backing up table before dropping
From:   barb.green

There are many reasons to make a local backup copy (if you have the room and the time) before maintenance or change implementation is done.

For me I do not drop anything, I rename if recreating.?? Exception tables that are locked by failed loads that can no longer be released.? I do this for all objects for ease of backing out any changes, simply rename again..?

I do this in all environments no matter what the instructions are from developers.? I often get requests that specify perserve the data, but the DDL they provide the first line is drop .?? It is important to know your data and if the object you are renaming has soft RI, make note of it and remove it from the renamed object.? If Join Indices are involved you will find you must drop the JI before you can rename so the order in which you process the request.

If your crew is doing an mload and it for some reason fails or they mess up the data you will find a local copy beneficial instead of having to restore from your backups, especially when the tables are large.

Beyond renaming I also do show ? helpstats exporting to a local file for all the objects for each change just in case,? I hate depending on others when this info might be necessary;

As always this is just what I do, your mileage may vary and your shop may have different rules/processes.

  <Prev Next>   <<First <Prev

  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 23 Jun 2019