I would try and read up about database normalization from a theoretical standpoint. E.g. here's a sample article http://databases.about.com/library/weekly/aa080501a.htm At the bottom of the page there are links to several related articles. -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Pallav Kalva Sent: vendredi, 18. juin 2004 11:15 To: oracle-l@xxxxxxxxxxxxx Subject: Re: Database Design questions I have been replying to messages but somehow may message doesnt go to the list, hope this one makes it. Thanks! for all your comments. I think , I should explain more about my application, the table which I showed is the data from one company for one type of property listing say "Preforeclosure" data. I will be having similar types of tables for different types of property listings like "foreclosures" , "Foresalebyowner" and from different companies. In that case I will end up with 10-20 tables each with 130 columnns.=20 Does it make sense to break the data into several tables and have one-to-one relationsips ? There would be some updates to the properties otherwise it is mostly showing property listings on our website.=20 ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------