I've added so many 2c this thread is nearly tax deductable! > .. I have never actually seen a Sybase instance go down > or mess up my data.
I have seen some large Sybase databases go down quite spectacularly. > The whole financial world seems to run on Sybase, and so far it's been > doing OK... Most of the web world runs on MySQL and does ok - just like CDBaby who used to have constraint and corruption issues until they switched to Postgres. > > The lesson here: Regardless of software, if your people can't make it > > work, it won't satisfy you. > Absolutely. But I have experienced three Oracle production enviroments, > all maintained by competent DBAs, all of whom spent quite a bit of time on > the phone with gold-pressed-latinum support only to be told: "yeah, sorry, > that's a bug", "We are working on a patch" or "It will be fixed in the > next version". Were they so good they only their funky pushing the system > to the max could reveal these bugs, or are there just so many bugs in the > system? Seems a common scenario in much of the "enterprise" software I have come across. CA is partucularly good at this sort of response. > > But, I still assert that, given equally competent people, modern Oracle > > is better than modern Sybase. Hands down. > I'd call it a draw, except that you need more experienced people to keep > Oracle ticking while someone like me can install and maintain a > high-concurrency heavily loaded Sybase enviroment with ease. You probably do need more people to manage Oracle in a big environment, but my opinion is that you end up needing more developers with Sybase because you end up needing more lines of code. That is a purely gut feel however. Further, my experience with large-ish (some millions of rows and many tables) databases is that Postgres scales to that size easily and needs even less support than Sybase. The support people probably need to be smarter though, especially if you use replication. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
