With today's hardware power, I think sqlite will easily scale to most solutions. You may have to purchase a bigger machine, but it is truly easy and the data file does not corrupt like Access. Access is a piece of trash.
I am helping a company currently with a system that gets 400 million records a month, but this is the only time out of numerous contracts we have had I have seen something this big. Oracle is just simply overkill is most cases today. As the speed of hardware increases, I think databases like Sqlite will take the for front because of simplicity. Oracle, and SQL server give you every possible configurable capability, but ironically the DBAs that configure this stuff don't really understand what they do. Most C programmers do but they are not DBSs. So for the fact you just throw statements at Sqlite, and it works, it would be an excellent choice for most solutions at this point. Plus you have the source, if something goes awry! Thanks, Allan -----Original Message----- From: Chris Carter [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 04, 2003 7:49 AM To: [EMAIL PROTECTED] Subject: FW: [sqlite] Big Players League > -----Original Message----- > From: Chris Carter [mailto:[EMAIL PROTECTED] > Sent: 04 November 2003 14:17 > To: 'D. Richard Hipp' > Subject: RE: [sqlite] Big Players League > > > [EMAIL PROTECTED] wrote: > > I fear this problem will become even more acute when PHP5 > comes out of > > beta. People will see that SQLite is bundled and wonder "Am > I suppose > > to use SQLite in place of MySQL now?" I think we need a guide for > > helping people to make that choice. We need to help people better > > understand when is it appropriate to use SQLite and > when MySQL > > is a better option. > > > > If any readers would care to attempt to write such > documentation, or > > even just start a Wiki page containing ideas of what such a > document > > should look like, your contributions will be greatly appreciated. > > -- > > D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565 > > Richard, > > I have only just arrived to sqlite and I haven't got a clue about how > it works (internals) but Windows users will understand the difference > between Jet databases (*.mdb) and SQLServer. Is this the kind of > analogy you are looking for between sqlite and big players? Only that > sqlite is miles better than jet! (I have my own horror stories about > jet). > > IMHO, some points to look for are: > - Enterprise or workgroup > - Centralized or standalone > - Built-in or runs externally > > Hope this helps. I guess the 3 items above are pretty much the same, > but just different view angles on the same thing. > > Cheers! > Chris > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
