Re: Questions about extremely large database support

2001-07-23 Thread Mike Baranski
On Saturday 21 July 2001 00:28, Jeremy Zawodny wrote: > On Thu, Jul 19, 2001 at 03:15:02PM -0500, Tom Wheeler wrote: > > Our two most important requirements for the database engine are > > speed and scalability. We will be inserting probably 5,000,000 > > records per day into our database > > Sou

Re: Questions about extremely large database support

2001-07-23 Thread Sergei Golubchik
Hi! On Jul 22, William R. Mussatto wrote: > > > > Well, on my tests I was able to add ~4,000,000 rows in 17 hrs > > with MySQL 3.23, and in 4 hrs in MySQL 4.0 > > > > Table had 4 indexes. Removing those increased the speed by > > several orders of magnitude (!!!). > > > > Hadware was moderate

Re: Questions about extremely large database support

2001-07-22 Thread William R. Mussatto
On Sat, 21 Jul 2001, Sergei Golubchik wrote: > Date: Sat, 21 Jul 2001 10:36:22 +0200 > From: Sergei Golubchik <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: Tom Wheeler <[EMAIL PROTECTED]> > Subject: Re: Questions about extremely large database support > > H

Re: Questions about extremely large database support

2001-07-21 Thread Sergei Golubchik
Hi! On Jul 20, Jeremy Zawodny wrote: > On Thu, Jul 19, 2001 at 03:15:02PM -0500, Tom Wheeler wrote: > > > > Our two most important requirements for the database engine are > > speed and scalability. We will be inserting probably 5,000,000 > > records per day into our database > > Sounds doable-

Re: Questions about extremely large database support

2001-07-20 Thread Jeremy Zawodny
On Thu, Jul 19, 2001 at 03:15:02PM -0500, Tom Wheeler wrote: > > Our two most important requirements for the database engine are > speed and scalability. We will be inserting probably 5,000,000 > records per day into our database Sounds doable--on reasonable hardware. > and will maintain around

Re: Questions about extremely large database support

2001-07-19 Thread Jeremy Zawodny
On Thu, Jul 19, 2001 at 11:30:31PM +0200, Werner Stuerenburg wrote: > > > Is there a really efficient way to implement a function like > > indexseek() in FoxPro? This function will simply check an index > > to tell you if a record with that key exists. Sort of like > > "select count(id) from Fo

Re: Questions about extremely large database support

2001-07-19 Thread Michael Meltzer
t;Tom Wheeler" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, July 19, 2001 4:15 PM Subject: Questions about extremely large database support > We are beginning a project and need to choose a database. We have been > using MS Visual FoxPro, which is like mySQL in tha

Re: Questions about extremely large database support

2001-07-19 Thread Werner Stuerenburg
> Is mySQL up to such a task? I have been using mySQL for four years > now, but have never used it in a project of this magnitude. We'll be > handling financial data in the database, so integrity is important. I think so. You find impressive statements on the mysql site about speed & si

Questions about extremely large database support

2001-07-19 Thread Tom Wheeler
We are beginning a project and need to choose a database. We have been using MS Visual FoxPro, which is like mySQL in that it is very fast and ISAM-based, but is used more often as a file database rather than client/server. Unfortunately, we are quickly approaching FoxPro's 2GB table size limit,