Re: varchar2(size)

From: joel garry <joel-garry_at_home.com>
Date: Thu, 1 Oct 2009 09:58:36 -0700 (PDT)
Message-ID: <8af3905e-7efd-40f7-a66b-36d5b787db8f_at_w37g2000prg.googlegroups.com>



On Sep 30, 4:35 pm, indytoatl <indyto..._at_gmail.com> wrote:
> On Sep 30, 3:48 pm, John Hurley <johnbhur..._at_sbcglobal.net> wrote:
>
>
>
> > On Sep 30, 3:19 pm, yf..._at_vtn1.victoria.tc.ca (Malcolm Dew-Jones)
> > wrote:
>
> > snip
>
> > > What if you need to save Mr. Seamus Wolfeschlegelsteinhausenbergerdorff's name in
> > > your database?  What if his daughter then gets married and hyphenates her name with
> > > her husband's?
>
> > > Many "maximum" sizes are really just arbitrary guesses.
>
> > Ahh then simply make everything varchar2(2000) that should fix it all
> > rightey eh?  No worries then make all your varchar2 fields like this
> > then ...
>
> > If you are just guessing then please stay away from my databases.
> > Rules can change over time and database systems can handle some
> > reasonable number of implementation changes when required.
>
> Thanks for the responses. I just wanted to be sure that the varchar
> size didn't have
> anything to do with SGA or buffer memory. So, you have comfirmed that
> there is no
> performance issues with different settings.
> with memory allocation within the SGA.

Well, do you consider PL/SQL memory? Do you think each users apps memory usage is going to affect your server memory? Go to tahiti.oracle.com and put varchar2(1999) in the search box. Then read what comes up and think about it.

jg

--
_at_home.com is bogus.
http://catless.ncl.ac.uk/Risks/25.79.html#subj12
Gee, why do some of those issues sound so familiar?
Received on Thu Oct 01 2009 - 11:58:36 CDT

Original text of this message