Dear Jerry Schwartz We have applications for colleges in India. The same idea of having single table for manipulating students records. but we are not following archiving concept.
Ex stupersonal. and stuclass these tables are playing wide role in our application. After 7 years now there are 9000 records[postgresql backend] are there in the table. Because of this the entire application [ Fees, attendance, exams etc] performance is getting down. For the remedy of this I proposed this year wise architecture for our new version [mysql]. I have problem in year wise also, i have number of mutual related tables for students such as stu_last_studies, stu_family_details, stu_address, stu_extracurri and so on. If i go for year basisis i have to make all the above tables also year basis. Hence, I feel it difficult have such number of tables after few years. As you said the archive system, can you the idea about the archive system[If needed i will give the table structures]. It will be grate help to me. Thank you VIKRAM A ________________________________ From: Jerry Schwartz <jschwa...@the-infoshop.com> To: Vikram A <vikkiatb...@yahoo.in>; Johan De Meersman <vegiv...@tuxera.be> Cc: MY SQL Mailing list <mysql@lists.mysql.com> Sent: Tue, 16 February, 2010 9:32:22 PM Subject: RE: how things get messed up >-----Original Message----- >From: Vikram A [mailto:vikkiatb...@yahoo.in] >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 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=vikkiatb...@yahoo.in The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/
