[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ale] SQL server recomendations
- Subject: [ale] SQL server recomendations
- From: greg at turnstep.com (greg at turnstep.com)
- Date: Tue, 14 Aug 2001 16:22:38 -0400 (EDT)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> slowdown on the input volume during the winter months. I
> realize I could use MySQL or PostGreSQL which are free, but
> due to the size of this thing, and the possibility of remote
> sync'ing, I'm guessing I should stick with one of the "big
> guys".
You should look at Postgres again - it is definitely now one
of the "big guys". Lumping it together with mySQL is not fair
to either one. MySQL is good for fast, simple transactions such
as running slashdot. Postgres, on the other hand, is a very
powerful, ANSI-compliant database that can handle a lot more than
most people think. I still think Oracle is the best overall
database, but the price for it is outrageous. If you can afford
it and are planning on doing a *lot* of business (on the order
of millions of records+) pony up for Oracle, but if not, go for
Postgres.
</twocents>
Greg Sabino Mullane
- ----------------------------------------------------------------
/~\ The ASCII
\ / Ribbon Campaign *greg at turnstep.com*
X Against HTML PGP Key: 0x14964AC8
/ \ Email! 200108141617
-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html
iQA/AwUBO3mHY7ybkGcUlkrIEQIzDgCgmefBv9vyNWkwqq5msqNceUjWW9sAoJDk
r3l9npS/JHWDjQ2QHlM9XSRO
=E2pC
-----END PGP SIGNATURE-----
--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.