Skip navigation links

MySQL Forums :: Partitioning :: Error 23, 1016: Partition with MyISAM


Advanced Search

Re: Error 23, 1016: Partition with MyISAM
Posted by: Rob Redmon ()
Date: April 01, 2009 10:33AM

First, I'm no DBA, nor a professional programmer. I'm a scientist and this is my opinionated perspective. I found that at 90million rows in one table, queries that should be well indexed were randomly slow and deletes were nearly impossible; corrupting the database in two cases and taking hours to complete in other cases. I'm sure some tuning is possible. Our DBA here counseled me to not put more than a few million rows in a table for the sake of 1) maintainability (e.g. deletes), 2) physical storage (we have small SCSI disks that are shared resources, ~75GB each). I also found insert speed falling off; sorry I don't have hard numbers to back that up at the moment.

The purpose of this file catalog is 2 fold:
1) to tell me exactly where each file lives (e.g. disk, tape, remote location),
2) remove redundant (md5sum) entries broadcast by multiple sources,
3) provide inventory summaries at various temporal granularities (hourly measurements, daily, monthly, etc)

I don't really know what data warehousing is but it sounds this is it.

Options: ReplyQuote


Subject Views Written By Posted
Error 23, 1016: Partition with MyISAM 9164 Rob Redmon 03/31/2009 09:07PM
Re: Error 23, 1016: Partition with MyISAM 4250 Phil Hildebrand 03/31/2009 11:35PM
Re: Error 23, 1016: Partition with MyISAM 3949 Rick James 04/01/2009 12:49AM
Re: Error 23, 1016: Partition with MyISAM 3728 Rob Redmon 04/01/2009 10:33AM
Re: Error 23, 1016: Partition with MyISAM 3790 Rob Redmon 04/01/2009 08:35AM
Re: Error 23, 1016: Partition with MyISAM 3916 Rob Redmon 04/01/2009 09:57AM
Re: Error 23, 1016: Partition with MyISAM 3560 Phil Hildebrand 04/02/2009 01:32AM
Re: Error 23, 1016: Partition with MyISAM 2992 Chris Slominski 06/02/2009 11:42AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.