RE: Expanding varchar2 column

Yes, I did indeed consider creating a similar table, enabling trace, and
inspecting the trace file.  As this is a very large table and there
wasn't a place to run a similar-sized test, the co-worker opted to not
run a test and, rather, to allow for adequate time during the change
window to accomodate a full table scan just in case that happened,
though we both felt quite sure that it would not.  I'm not a guru but
far from a novice.  As this was for a co-worker, I was simply asking if
anyone knew for sure.  Thank you for your response.
 
Mark
 

        -----Original Message-----
        From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Paul Baumgartel
        Sent: Tuesday, November 15, 2005 6:30 PM
        To: oracle-l@xxxxxxxxxxxxx
        Subject: Re: Expanding varchar2 column
        
        
        Mark,
        
        I'd think that the procedure would be the same regardless of the
table's row count--have you considered creating a similar table,
enabling trace, and inspecting the trace file?
        
        -- 
        Paul Baumgartel
        paul.baumgartel@xxxxxxxxxxxx
        
        
        On 11/15/05, Strickland, Mark < mark.strickland@xxxxxxxxxxxx
<mailto:mark.strickland@xxxxxxxxxxxx> > wrote: 

                A co-worker needs to modify a varchar2 column from 100
bytes to 200 bytes in a large table.  We think that it will just modify
the data dictionary and not do a full table scan.  Does anyone know for
sure?  Yep, I've RTFM'd and google'd and metalink'd it.  Thx.
                
                 
                Mark Strickland
                Seattle, WA

Other related posts: