You can use either - as you probably know. What do you want? How would
*you* decide what is "best"? If you're after performance you can get
the same out of each, but you will need considerably higher spec'd
hardware to get the same performance on Oracle as you get on jBASE. All
things being equal then, you can expect to get better performance
running T24 on jBASE.
Mike.
Pros of Oracle;
Easily available DBA skills
Industry standard data access
Removes the need for jBase file sizing
Improved Backup technology - Hot backup, Flash etc.
Distributed app/db server possible
Distributed Database servers possible
Of the above it should be noted that jBase 5 has 'dynamic' files which
also do away with the need for re-sizing.
Cons of Oracle:
XML storage may not be widely used
Overhead of parsing XML may expose poor coding; resulting in loss of
performance
Yes, i know, but
1) JBASE does not have same security functions which has ORACLE
2) For higher spec'd you can wath this site
http://goliath.ecnext.com/comsite5/bin/comsite5.pl?page=description&item_id=0199-105806&purchase_type=ITM
please read the tests
<The results demonstrate that a bank could perform account accruals
across 13 million accounts in less than 14 minutes and process over 55
million online transactions per eight hour day>
what you can tell about this?
But.. I see no comparison of the same hardware and a native jBASE database
version of Temenos....
So, all you know is that T24 runs well on big-iron HP with Oracle...
Regards
Simon
=======================================
Simon Verona
Director
Dealer Management Services Ltd
si...@dmservices.co.uk
=======================================
Native jbase will always be cheaper than oracle per-click...
Simon
=======================================
Simon Verona
Director
Dealer Management Services Ltd
si...@dmservices.co.uk
=======================================
-----Original Message-----
From: jB...@googlegroups.com [mailto:jB...@googlegroups.com] On Behalf Of
John Watson
Sent: 16 January 2007 10:24
To: jBASE
Subject: Re: Oracle or JBASE
What features you specifically looking for ?
Simon
=======================================
Simon Verona
Director
Dealer Management Services Ltd
si...@dmservices.co.uk
=======================================
-----Original Message-----
From: jB...@googlegroups.com [mailto:jB...@googlegroups.com] On Behalf Of
Ramin.Ha...@gmail.com
Sent: 16 January 2007 11:40
To: jBASE
Subject: Re: Oracle or JBASE
> -----Original Message-----
> From: jB...@googlegroups.com [mailto:jB...@googlegroups.com]
> On Behalf Of Ramin.Ha...@gmail.com
> Sent: 16 January 2007 15:40
> To: jBASE
> Subject: Re: Oracle or JBASE
>
>
1. Functionality.. you are using T24? I don't know T24 but I presume that
the application functionality of T24 is equal on Oracle or jBASE databases..
I'm presuming that T24 updates Oracle through a Jedi interface?
2. Performance - I would estimate that native jBASE would be faster than
Oracle.
3. Security - difficult one to answer. Oracle has more security
configuration than jBASE, but I wouldn't say that jBASE is inherently
insecure - it uses operating system level security to secure the database.
4. Lost Data - in normal use, zero (I'd be worried if Oracle lost 0.1% of my
data!).. Do you mean "lost" as in requiring defragmeting or something? Or
are you worried about server crashes? jBASE has Transaction Journalling
which reduces data loss after a crash.
5. Clusters - yes, Oracle has clusters, jBASE doesn't. If you need
clustering of the database then it sounds like you need Oracle. (remembering
of course that jBASE requires less hardware than Oracle for the same no of
transactions)
To be honest, I would have thought that Temenos would be better served to
assist you with the decision on what database to use. They will be able to
review your requirements and match them against what T24 can do with each
database.
Hope this helps
Simon
=======================================
Simon Verona
Director
Dealer Management Services Ltd
si...@dmservices.co.uk
=======================================
-----Original Message-----
From: jB...@googlegroups.com [mailto:jB...@googlegroups.com] On Behalf Of
Ramin.Ha...@gmail.com
Sent: 16 January 2007 12:18
To: jBASE
Subject: Re: Oracle or JBASE
Since T24 was built on jBASE and jBASE is faster, smaller, and in my
experience more reliable I would go with jBASE.
The only reason I would go with Oracle personally would be if there were
other Oracle based applications that were going to look at the data.
Deschutes County Information Technology
Emery Grantier, Senior Programmer Analyst
14 NW Kearney
Bend OR 97701
Help Desk (541) 617-4759
Voice & voice mail (541) 388-6543
Fax, with cover sheet! (541) 317-3180
Working hours *EMERGENCY* pager 330-3001 or ePage
"Everything should be made as simple as possible, but no simpler."
-----Original Message-----
From: jB...@googlegroups.com [mailto:jB...@googlegroups.com] On Behalf
Of Ramin.Ha...@gmail.com
Sent: Tuesday, January 16, 2007 9:42 PM
To: jBASE
Subject: Re: Oracle or JBASE
I work with Temenos Globus G12, but the bank I'm working for looks for
T24 and has the same problem, Oracle or jBase. My experience and
knowledge of jEdi (this layer of jBase which allows to use Oracle)
tells me that T24 (the same as G12, G13, ... ) would work faster with
jBase. Relational Oracle DB does not fit multivalue concept which was
used in Globus. The only pros for Oracle, from my point of view are:
* administration - which are backups, monitoring, etc. is better for
Oracle
* in jBase 5.0, i'm not sure of this, there are no more XML blobs, but
typization is used
"The only reason I would go with Oracle personally would be if there
were
other Oracle based applications that were going to look at the data."
I don't think, that access to Globus DB (when it sits at Oracle) would
be useful for satelite products, still it is a multivalue concept,
implemented with XML in a releational DB,
I don't suppose - the access would be allowed by Temenos,
Kind regards
Leszek
What I have seen is that in case of T24, Oracle is only used as a
storage area where all your data is stored in XML tags, nothing more
than that. The only thing you get is Clustering in Oracle. You cant
even create a new file in Oracle directly, you will have to give a
command in JBase with type set to XMLOracle and then it will create
your file in Oracle. At the same time it can manage HUGE data but there
are a lot of over heads, like your query passes from thin client
(Browser) to T24, to JBASE layer JEDI, to OCI driver which converts
into SQL which then reads from Oracle which is in XML form, gets your
data and all this process goes back to show you the result!!!! not good
enough.
Where as T24 is built on JBASE, you get T24 and Jbase comes along with
it on the same application layer. Obviously it will give functionality,
performance and every thing nice as T24 is designed on Jbase where as
because of its Open architecture it can CONNECT to other products and
CONNECTING to a product is always slower....
I hope i clarified the point....
--
Thank you and Regards,
Foong Yee
Thank you for your contribution to this interesting thread. As Database
Strategy Manager for TEMENOS I thought I'd best contribute myself at
this point.
Firstly we offer a multi database solution and deliver commercially
proven and acceptable solutions on jBASE, Oracle, DB2 and SQL Server.
All are "good enough" (to quote your words) and are being enjoyed
by various significant organistations around the globe.
The decision to take the variants is never, if rarely a technical one.
There are a myriad of reasons why a company would choose an Oracle
solution over jBASE and visa-versa. They may already have expertise in
a particular DBMS or they may have a company policy in place. The
decision tends to be made on a combination of cost, performance,
resilience or commercial perception with different things being
important to different organisations.
Unfortunately part of your technical description is a little misleading
because the "layers" you describe actually exist in all 4
solutions. Browser, T24/jBASE, jEDI are present regardless of the
backend. In the case of Oracle OCI is the most efficient connectivity
method but we do not convert to SQL, we use Xpath.
The comments about the 'only thing you get is clustering in Oracle"
is false but as I say the decision to go with a certain database does
not revolve around technical detail.
The point is we offer a choice of four commercially viable and proven
solutions; you pays your money and takes your choice.
Regards
Clive A Ketteridge
Database Strategy