RE: Varchar2....is this Dilbert or what?????

     There is no advantage to making them all 255 (I'd ask them where they got the magic number, why not 256?). The problem with making the column bigger is on the application side, not the database side "alter table xxxx modify(col1 varchar2(30))" can be run anytime the app is capable of handling the larger value.                  

-----Original Message-----
From: Christine Turner [mailto:christine.turner_at_ips-sendero.com] Sent: Tuesday, May 09, 2000 6:04 PM
To: Multiple recipients of list ORACLE-L Subject: Varchar2....is this Dilbert or what?????

Ok, forgive me if I offend anyone....but the head honchos came and asked what the ramifications would be if we were to make every, yes EVERY varchar2 column in new database the length of 255. The reasoning behind this is...."to keep maintenace down in the future, so we don't have to change the database every time when need a column resized". I'm fairly new to being a database administrator (going on a year), but I have been working in Oracle for about 6 years and quite frankly this sounds totally obsurd! Anyone have any comments??? Pro's, Con's????

Thanks In Advance,
Christine Turner
FTP Database Administrator
IPS Sendero
Phone: (800) 321-6899 ext. 3286
Fax: (480) 946-8224
E-mail: christine.turner_at_ips-sendero.com

-- 
Author: Christine Turner
  INET: christine.turner_at_ips-sendero.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).