Link to home
Start Free TrialLog in
Avatar of deepakabc
deepakabcFlag for Australia

asked on

orcale vs firebird vs db2 vs mssql

Hello

currently i m using firebird. i m just wondering what will be the advantage on firebird if i move to oracle or db2 or mssql.

oracle is expensive but is it worth to look in to it ?

why orcale is better than other databases ?

Avatar of Guy Hengel [angelIII / a3]
Guy Hengel [angelIII / a3]
Flag of Luxembourg image

it depends on what you need.
yes, oracle is expensive, at is has many advanced features. so, if you need such features, you need oracle.
if you don't need those features, you don't need to buy oracle.

so, you need to clarify the "specs" of your database system like:
* backup&recovery features
* overall size
* large table sizes
* query syntax features
* full-text indexing
* replication
* ... etc etc etc
Hi deepakabc

I should go for DB2, not because I liek to, but because ther is no other real option.

Oracle has some annoying bugs
and I don't like to put my important data in the Claws of Microsoft.
So DB2 is the only good solution, on top of that is DB2 fast and reliable I work with it for 25 years and we never had problems of any kind. There is an application in this company that use Oracle and the quality of the data we get delivered from there is real poor.

Regards,
Murphey
I cannot hold back, but:

>Oracle has some annoying bugs
that's the case for all products I know... you cannot tell me that DB2 does not have any bugs?!!
if you said: because an oracle database is much more difficult to handle/tune etc, that would be ok as argument.

>and I don't like to put my important data in the Claws of Microsoft.
that's an opinion, but not a reason to avoid MS products. they also have bugs, but we discussed that point. anything else is just "personal issue".

>There is an application in this company that use Oracle and the quality of the data we get delivered from there is real poor.
the fault can be as well the application code/design as the oracle tuning/indexing etc.
get a real application/db analyst to look at that, and the app should become just fine.

btw, the quality of data is not the responsibility of the database product, but of the design, the application and the users ...
Hi Angellll,

personal opinion or personal experience, one can't exist without the other?

The bug in Oracle that is the worst is the missing auto-sequence while writing records and the workaround that does not work.

I never did a DB2 upgrade and have to pray that it will work, I don't know any Microsoft product that is 100% upwards compatible or where the documentation covers all new changes, improvements and corrections.

But maybe this is less important information for some people, after all these years I learned that the most decisions are based on  company politics or price.

Best regards,
Murph

>The bug in Oracle that is the worst is the missing auto-sequence while writing records and the workaround that does not work.

that's not a bug... the SEQUENCE + TRIGGER method works just fine.
admitted, a bit more of work, but much more flexible on the other hand !!

>I don't know any Microsoft product that is 100% upwards compatible or where the documentation covers all new changes, improvements and corrections.

you meant downward compatible... while MS tries to do so, but obviously they cannot.
and when try stick too long, they stick with bad stuff, so getting rid of backward compatibility is sometimes a "must" for them.

actually, the documentation exists. but there is SO MUCH documentation, you can't find the "summary" stuff, or just get lost in the details. yes, MS docs are really improvable


>But maybe this is less important information for some people, after all these years I learned that the most decisions are based on  company politics or price.

I could not write it better :(

Hi Angellll,

That's exactly what I mean, the SEQUENCE is working fine, but for a DB it has to work Good or great.
A SEQUENCE is nice to have if it is used in only one application, but as soon as two applications try to get a sequense number the same time, the same sequence number is supplied by the SEQUENCE.nexval function and as fat as I know is it impossible to lock a sequence before update. The question is how big is that chance that this will happen? Pretty big, between 2 and 15 times a week in 1500 sequence numbers. Real bad if it should be a foreign key.

Regards,
Murph
>A SEQUENCE is nice to have if it is used in only one application, but as soon as two applications try to get a sequense number the same time, the same sequence number is supplied by the SEQUENCE.nexval function a


this is WRONG. oracle guarantees that the sequence object does NOT return the same sequence number twice !!!!
I don't know where you got that information from, or how you experienced that, but it's definitively working correctly even in multi-user/session situations!!!

for the reference:
http://www.techonthenet.com/oracle/sequences.php
official reference:
http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/statements_6015.htm

starts with:
Use the CREATE SEQUENCE statement to create a sequence, which is a database object from which multiple users may generate unique integers. You can use sequences to automatically generate primary key values.

Hi deepakabc,

Jumping in and (hopefully) back on topic.....

I've got a pretty good background with Oracle, DB2, and MySQL.  If I've got a "real" IT budget, I'll almost always choose DB2.  Most studies show that TCO is less for DB2 than for Oracle.  Plus, I like the DB2 extensions to SQL better than the Oracle extensions.   One last plug for DB2 is that I prefer the DB2 administration to Oracle administration.  Oracle probably has more tools, but my experience is that Oracle is also more complicated to administer.

If your IT budget is tight, look at MySQL.  It's very solid and performs quite well.  It's not as feature rich as DB2 or Oracle, but it does everything that most shops require.  Note that if your database is going to be large (100s of gigs or larger) with a high transaction rate, you'll want DB2 or Oracle.  MySQL can't keep up with "the big boys" on the largest, most demanding databases.


Good Luck,
Kent
Avatar of deepakabc

ASKER

i m currently using firbird database.

what advantage i will get if i move to db2 ?
ASKER CERTIFIED SOLUTION
Avatar of Kent Olsen
Kent Olsen
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial