Re: Large Key and Lots of Column

In article <3q8b5e$30o_at_portal.gmu.edu>, Dong Duong Nguyen (dnguyeb_at_osf1.gmu.edu) writes:
>
>Hi,
> I appologize if this is a stupid question.
>
> I have a 1 table application that contains a 1 field key.
>This key is 55 varchar2 big. This also has 25 fields. Half of them are
>only 1 character fields however. Three fields are 2000 varchars in size.
>
> We decided to do this to keep things simple. However, will the large
>key and large number of columns cause any performance problems. Should I try
>and use some kind of numeric surrogate for the key. Should I also try to
>break the table up.
>
>Thanks doug
>
G'Day Doug,

If the key column is unique, I might use a sequence number.

Don't know if you gain much of an advantage by breaking the table up into multiple tables, not if your key is 55 characters long.

Normalisation of tables is usually preferrable.

Regards,
Alex Long

--
                          ,     \    /      ,
                         / \    )\__/(     / \   
                        /   \  (_\  /_)   /   \                
 ______________________/_____\__\_at_  @/___/_____\________________ 
|paladin.along.dialix.oz.au 					|
|Alex Long 		   					|		
|Adelaide, South Australia 					|
|_______________________________________________________________|
|Billy, in one of his nice new sashes,         			|
|Fell in the fire and was burnt to ashes;    			|
|Now, although the rom grows chilly,           			|
|I haven't the heart to poke poor Billy.          Harry Graham. |
+_______________________________________________________________+
                   |    /\ /      \\       \ /\    |             
                   |  /   V        ))       V   \  |
                   |/     `       //        '     \|
                   `              V                '
                   
_