Re: 50M records each year.. how to handle

You mean your app creates 50M records each day !! Can you please elaborate on what type of partitions and storage engine are you using ? Thanks SN Personally I'm always ready to learn, although I do not always like being taught From: Krishna Chandra

Re: 50M records each year.. how to handle

Hi Sudhir, I am handling 50M record each day. Your requirement can be easily full filled using partition and good architecture. Thanks, Krishna On Mon, Nov 2, 2009 at 2:57 PM, || Sudhir Nimavat || < sudhir_nima...@yahoo.com> wrote: > I have come across a requirement where I need to store a ver

RE: 50M records each year, help me choosing the stretegy

Sudhir, please remove the || from your name in your email: "|| Sudhir Nimavat ||" We have about 1 BILLION rows of data here and we do a few tricks which may or may not be of interest to you. For starters, setup replication and write to a master and have at least 2 slaves. This makes backups MUCH

Re: Trouble joining 3 tables

Yes, I don't see why that wouldn't work... On Mon, Nov 2, 2009 at 11:09 AM, Brian Dunning wrote: > Johnny - Your solution might actually help me solve my next step, which is > to also return a count of pets bought only within the last 7 days. Something > like this: > > > >> SELECT people.*, >>

Re: Trouble joining 3 tables

Johnny - Your solution might actually help me solve my next step, which is to also return a count of pets bought only within the last 7 days. Something like this: SELECT people.*, SUM(IF(cars.id IS NULL,0,1)) AS car_count, SUM(IF(pets.id IS NULL,0,1)) AS pet_count, SUM ( IF ( pets.d

Re: Trouble joining 3 tables

Thanks, this solved it! On Nov 2, 2009, at 12:37 AM, Michael Dykman wrote: I suspect 'distinct' might help you out here. SELECT people.*, count(distinct cars.car_id) as car_count, count(distinct pets.pet_id) as pet_count -- MySQL General Mailing List For list archives: htt

Re: Trouble joining 3 tables

You are asking for all records form all tables. So, If 1 person has 1 car and 1 pet, there will be 2 records returned for that 1 person. You'll need to use SUM() instead of COUNT(): SELECT people.*, SUM(IF(cars.id IS NULL,0,1)) AS car_count, SUM(IF(pets.id IS NULL,0,1)) AS pet_count, Ma

Southern hemisphere polar alignment // I/C Mr. Rob Kanen

Dear Rob: I live in Brazil, have a SkyWatcher EQ6 pro mount (with a GPS module) and a William Optics 132 FLT refracting telescope. I plan on doing my observations between the towns of Canoinhas and Tres Barras, in the State of Santa Catarina (second southernmost State in Brazil - lats. approx. -26º

Re: Fw: 50M records each year, help me choosing the stretegy

Sudhir: do yourself a favr and split the blobs (=body) off to a different table. Most fo the time bodies are not used, only when the actual email needs to be shown. That means that you can keep the frequently used fields together in a table for much quicker access. cheers, Walter On Mon, Nov 2,

Fw: 50M records each year, help me choosing the stretegy

Its a very simple table that will store messages. Each message would have subject, body,to_user_id, from_user_id,is_deleted,date_sent and may be one or two more column There would be frequent read operation and slow write operation. Thanks SN Personally I'm always ready to learn, alt

Re: 50M records each year, help me choosing the stretegy

sudhir543-nima...@yahoo.com wrote: I have come across a requirement where I need to store a very large amount of data in a table. In one of our app.. we can have around 50 Million records each year.. Can any one guide me in choosing a strategy than can handle this load. 50M records is not th

50M records each year, help me choosing the stretegy

I have come across a requirement where I need to store a very large amount of data in a table. In one of our app.. we can have around 50 Million records each year.. Can any one guide me in choosing a strategy than can handle this load. Thanks SN Sudhir NimavatSenior software engineer

50M records each year.. how to handle

I have come across a requirement where I need to store a very large amount of data in a table. In one of our app.. we can have around 50 Million records each year.. Can any one guide me in choosing a strategy than can handle this load. Thanks SN Sudhir NimavatSenior software engin

Re: Raid level suggestions for mysql-server

In one of the more effective high-loads shops I have worked in, we deployed RAID 1 for logs and RAID 10 for data. The number of disks we put into those RAID 10's depended on anticipated load of the specific application. We often found ourselves needing additional spindles to meet high I/O needs,