Re: DB Comparisons

Yes, I have heard from another that PostGreSQL was something to look into for my particular project/site. I'm developing a board site where by webmasters can sign up for their own board. One guy recommends PostGreSQL for it's locking technique. I don't know how scalar this RDBMS package is though and how many queries can it withstand. Vbulletin.com, a standalone script written for MySQL are already getting nasty results on just one board. Sites are reporting database corruption with MySQL or heavy hardware usage. Hardware won't be a problem all that much in my case, I'm just worried about the RDBMS package. After hearing that MySQL has corrupted databases and cannot be revived unless through a backup has me worried. Currently, I'm down to choosing either Oracle, Sybase, and PostGreSQL. According to Oracle rep, Sybase is almost equivalent to Oracle and PostGreSQL seems to be a top choice among the developers I talked to. On 19 Nov 2000 07:02:44 -0800, ncrause@mweb.co.za ("Nathan Crause") wrote: >Unfortunately, my experience with Oracle is limited to hear-say from others >who work with it. Needless to say, the feedback is rarely ever good. It may >be a big, powerful RDBMS, but from what I've heard, it VERY slow and >incredibly resource hungry. > >As you stated, MySQL is lacking in features - I've come across this myself. >I even found that certain SQL-92 functionality wasn't supported. > >So date, I'm pretty content with PostgreSQL. I've never had it fall over or >have any trouble, and it performs very well. The JDBC which comes with it is >not 100% complete, but it's functional enough to use it for applications. > >None of the other RDBMS's you've mentioned I've come across. As a side not, >I'd suggest NOT using Microsoft SQL. It's VERY bloated (we require 1GB of >RAM to handle just 500 customers) and it's scalar and date functions are >unlike anyone else's. Again, it's one of those cases when it's MS or >nothing. > > > >"Jonathan Chum" <jchum@techdevelopers.com> wrote in message >news:3a16f55e.512527315@news.php.net... >> I'm trying to decide what SQL db I should go forth with. Currently I'm >> developing a forum which may later on be turned into a co-branded >> service and if it becomes very popular, will result into some >> unforseen trouble if I don't choose the right DB to work with. >> >> MySQL is what I'm currently developing in, but lately, I'm hearing >> that very large traffic sites are having their DB corrupted and >> unrecoverable because they didn't back up their tables. This scares me >> a bit. Also, I heard that MySQL was developed ground up for speed not >> performance, so you loose alot of features. >> >> PostGreSQL was recommend by another because it has an excellent table >> locking feature so queries will be queued efficiently. >> >> Oracle was something I looked into. It's heft on the price tag, but >> I'm looking to port the board once I gain enough money to purchase a >> license. >> >> Sybase is something that are popping up in Vbulletin.com that looks >> promising too. Some of the boards have over 600 users logged in at >> once are not going down. MySQL can handle alot of concurrent users at >> the price of hardware upgrades. >> >> Inprise is something I'm not too familar with, but might be worth the >> look since it's open source and free (I believe). >> >> I'd like to know what do you think about all of these databases I >> mention. The features, power, hardware, cost, etc. I'd like to weigh >> in all the suggestions I can get before determining which way I will >> go. Thanks >> >> -- >> PHP Database Mailing List (http://www.php.net/) >> To unsubscribe, e-mail: php-db-unsubscribe@lists.php.net >> For additional commands, e-mail: php-db-help@lists.php.net >> To contact the list administrators, e-mail: php-list-admin@lists.php.net >>