Welcome To The Home Of The Visual FoxPro Experts  
home. signup. forum. archives. search. google. articles. downloads. faq. members. weblogs. file info. rss.
 From: Jun Tangunan
  Where is Jun Tangunan?
 Cabanatuan
 Philippines
 Jun Tangunan
 To: Samir H.
  Where is Samir H.?
 Yogyakarta
 Indonesia
 Samir H.
 Tags
Subject: RE: Table with large memos
Thread ID: 268876 Message ID: 268900 # Views: 35 # Ratings: 0
Version: Visual FoxPro 9 Category: Databases, Tables and SQL Server
Date: Thursday, July 15, 2010 10:02:18 AM         
   


> > It depends...
> >
> > 1. Address - The format of address can be optimized to be stored in another table instead
> > 2. Teacher notes - how many teachers? If more than one then another table may be needed
> > 3. General Attitude - it may remain in the main table if it is as simple as it is
> >
> > When we talk about performance gain, a single table with all the data in it may be faster in a multi-user/shared environment but when the table becomes very large, the performance gain is decreased.
> >
> > In a client/server environment, it is always better to store your data into identities depending on the data you store - normalize your data.
> >
> > For example, the teacher notes (if more than one teachers make notes for a particular student) should be stored in a separate table. The address in Indonesia may not be similar to the address format of the Philippines so it is hard to comment on how to optimize it using another table. In my systems, the address is stored in several components not as a one whole string so I store them in a separate lookup table.
>
> Thanks for tips, Tom.
> For now, teacher notes are written by 1 teacher only and are only kept for 1 semester, but that may change in future. So I will move that field to another table.
> The address is one whole string, since there is no consistent address system to rely on (besides other fields like city and region). Do you mix addresses from different files in your address lookup table? For example student and employee addresses in one file?
>
> Regards
> Samir

To me, the main reason why I would break a memo field away from the original table into another table is when that memo field can be reusable. If not, why move it away?


http://www.junblogs.com/
http://weblogs.foxite.com/sandstorm36/default.aspx
http://www.coderisland.com/forum/viewforum.php?f=10

ENTIRE THREAD

Table with large memos Posted by Samir H. @ 7/15/2010 7:32:34 AM
RE: Table with large memos Posted by Tom Saddul @ 7/15/2010 8:55:33 AM
RE: Table with large memos Posted by Samir H. @ 7/15/2010 9:23:20 AM
RE: Table with large memos Posted by Jun Tangunan @ 7/15/2010 10:02:18 AM
RE: Table with large memos Posted by tushar @ 7/15/2010 10:15:10 AM
RE: Table with large memos Posted by Samir H. @ 7/15/2010 11:04:13 AM
RE: Table with large memos Posted by Samir H. @ 7/16/2010 4:58:46 PM
RE: Table with large memos Posted by Stefan Wuebbe @ 7/16/2010 6:45:05 PM
RE: Table with large memos Posted by Samir H. @ 7/17/2010 5:52:52 AM