>-----Original Message-----
>From: Vikram A [mailto:vikkiatbipl@stripped]
>Sent: Friday, February 12, 2010 4:13 AM
>To: Johan De Meersman
>Cc: MY SQL Mailing list
>Subject: Re: how things get messed up
>
>Sir,
>
>Thanks for your suggestion,
>I will go for blob storage, because our application will maintain the data on
>yearly basis[stupersonal2008, stupersonal2009 etc.]. So i feel we may not
>face
>such kind of performance issue in our application.
>
[JS] It sounds like you are planning to have one table per year. Regardless of
where you put your blobs, I think that is a bad idea from a design standpoint.
It will make it harder to find historical information.
If your database is relatively small, then I'd just keep everything in one
table. If it is big, then roll data that is five years old into an archive
table. That will give you only two places, and an easy-to-follow rule to tell
you where to look.
Regards,
Jerry Schwartz
The Infoshop by Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
www.the-infoshop.com
