Dossy Shiobara said: > I just have to ask: what version of Sybase and Oracle are you comparing? 9i and 11.92, 12, 12.5.
The worst Oracle instance was maintained by a couple of very good DBAs, at least according to the guy who actually worked for Oracle and did an audit of our system. They were doing a release on a weekend which included some complex SQL query of mine to update a lot of data. The DBAs phoned me late in the afternoon saying my query had been running for the past 4 hours. WTF!? Of course I got the blame and they ended up rolling back the release. Knowing i wasn't dumb I pleaded for them to give me access to the live system on Monday so I could inspect the thing. A query plan showed it decided to do a carthesian join on a couple of 100K row tables for no reason other than it being bored. No amount of updating statistics and index hints could convince it otherwise. On the UAT system it ran fine. I ended up just messing around with it (knowing it must have been some obscure bug) and after changing a join to a sub-query (or vice versa, can't recall) Oracle suddenly behaved and ran the update in a couple of minutes as I suspected it would in the first place. That is probably the worst thing I came acros, but there have been other instances. > to MySQL/PostgreSQL than it is to Oracle, in terms of capability and > stability. Not sure about that, I have never actually seen a Sybase instance go down or mess up my data. To be fair, I can say the same about Oracle. On the capabilities side, Oracle Analytics in 10g are very good, but other than that I don't see Oracle offers anything more. And don't get me started on the performance of Intermedia! The whole financial world seems to run on Sybase, and so far it's been doing OK... > 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? They also _still_ have a bug in either their connection library or only JDBC that has been around since version 7. I forgot the error string, but everyone and their brother is compaining about it on the internet. It seems to mostly happen after an SQL error that the connection becomes stale. Yet it is almost completely unreproducable and so still not fixed. Very poor if you ask me. We have a client running a heavily loaded system that is very affected by this. Their EJB server (Orion) tends to crap out when this happens in a transaction and leaves entity beans locked, meaning they have to restart the damn thing anything from a couple of times a week to several times a day. > 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. I don't feel like rubishing Oracle just for the fun if it or because I don't like working with it, that's not the kinda guy I am. But these are my very real life experiences... Cheers, Bas. -- 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.
