Hi, Would anyone be able to confirm that mysqld-max-nt.exe does not have a 4 GB limitation. I'd like the DB to go up to 40GB and 330 million rows. I am flexible, I'll use the biggest DB I can create.
ISAM seems to be the obvious choice but would INODB perform better on inserts for a large DB, since I got two indices besides the primary key: "It is a common situation in a database application that the primary key is a unique identifier and new rows are inserted in the ascending order of the primary key. Thus the insertions to the clustered index do not require random reads from a disk. On the other hand, secondary indexes are usually non-unique and insertions happen in a relatively random order into secondary indexes. This would cause a lot of random disk I/Os without a special mechanism used in InnoDB. ... The insert buffer is periodically merged to the secondary index trees in the database. Often we can merge several insertions on the same page in of the index tree, and hence save disk I/Os. It has been measured that the insert buffer can speed up insertions to a table up to 15 times. " Thanks > could you switch to the max version of MySQL. This would increase > you database size to some 2**64. > > Just install mysqld-max-nt.exe as your service to enable the > support for 64 bit pointers. > > The only manual work you will have to do is to copy record for > record from the old file to the new file. > > Your application does not have to be changed. > > Erich > > Brian Seccombe wrote: > > Hi there, > > > > I hope I am doing this right. We have a table running on a > Window NT server > > on a NTFS partition. We are using MySQL 3.23.52-nt. The name of > the database > > is scan, and the table in question is called scan too. > > > > We are a transport company, and store in this database a > scanned copy of all > > the days POD's. This has grown rather fast and we have now > reached the 4 gig > > default for a table. I have read that you can modify it too go > above this by > > altering max rows, etc. however it does not seem to make a difference. > > > > Is there an easy way to make a table that essentially has no > limit except > > the size of the hard drive? > > > > Many Thanks, > > > > Brian > > > > > > > > --------------------------------------------------------------------- > > Please check "http://www.mysql.com/Manual_chapter/manual_toc.html"; before > posting. To request this thread, e-mail [EMAIL PROTECTED] > > To unsubscribe, send a message to the address shown in the > List-Unsubscribe header of this message. If you cannot see it, > e-mail [EMAIL PROTECTED] instead. > > --------------------------------------------------------------------- Please check "http://www.mysql.com/Manual_chapter/manual_toc.html"; before posting. To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, send a message to the address shown in the List-Unsubscribe header of this message. If you cannot see it, e-mail [EMAIL PROTECTED] instead. --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
