I am looking for a BDE alternative. I looked at Apollo and Advantage, and I
like Advantage, but I have seen alot of posts for DBISAM. Is that a better
solution? Can you still get Advantage for free?
Jim.
Paul / ColumbuSoft
www.columbusoft.com
Jim Heinz <jhe...@ExtraSoft.com> wrote in message
news:8ucfl1$dt...@bornews.inprise.com...
I read a post where DBISAM is much faster than Advantage. If they use
proprietary file types, isn't that comparing apples to oranges?
Jim
"Sue D. Nom" <su...@courthouse.com> wrote in message
news:3A09C35D...@courthouse.com...
> I've never used DBISAM, but have used Advantage and find it to be fast,
well
> supported, and feature filled. Advantage desktop is free.
>
> Jim Heinz wrote:
>
Anyway... check it out.
http://www.elevatesoft.com/benchmrk.htm
Best Regards,
David Saracini
Also, Advantage is free for local server (multi-user, network, but not
client-server). You can't go wrong with it. :-)
Also, I just got back from the Advantage training, and the new 6.0 release
is damn cool. The data dictionary capabilities (default values, primary
indexes, referential integrity, user/group support and views) are all
awesome. They work with both Local and Remote servers. In addition, there is
their new "Extended Procedures" that let you run stored procedures on the
server.
In any case, for $0, how can you go wrong? :-)
--
Tim Sullivan
Unlimited Intelligence Limited
Dimethylaminoethanol for your software
http://www.uil.net
"Jim Heinz" <jhe...@ExtraSoft.com> wrote in message
news:8ucfl1$dt...@bornews.inprise.com...
<< DBISAM has a speed comparsion page on there site. It includes all of the
major players. I was impressed by the compressions. It wasn't just like
"select * from foo" where foo is a 10,000 record table. They had like more
than 25 different tests listed (along with the sql example) *AND* they
didn't claim that DBISAM won every test. Some times the DBISAM would win...
sometimes Advantage... sometimes the BDE. >>
One thing to note - since we put up that benchmark page Extended Systems has
contacted us and informed us that some of the poor results for Advantage
were due to the fact that the engine cannot optimize the BETWEEN operator
(and a couple of others such as LIKE and IN, I believe). If you change the
BETWEEN operators in the queries to use >= and <= instead Advantage will get
significantly better results. DBISAM still will win overall, but the margin
is much smaller.
We will be posting a new set of benchmarks as soon as possible that take
this into account along with an increase in the size of the main table to
100,000 records.
--
Tim Young
Elevate Software
www.elevatesoft.com
Is 6.0 actually released? I was on there site and I really couldn't tell
what version they were on. I read the "Upcoming features..." link and it
does look good, but it looked like it was still in development with no
release date listed.
Additionally, it doesn't appear that you can do transaction with "local
server". Is this correct? If so, that seems pretty limiting. I know that
you can do them on DBISAM.
Thanks and best regards,
David Saracini
>Additionally, it doesn't appear that you can do transaction with "local
>server". Is this correct? If so, that seems pretty limiting. I know that
>you can do them on DBISAM.
I have written subclasses of the Advantage components TAdsConnection
and TAdsTable that simulate 'local transactions' much like they exist
on Paradox and dBase in the BDE (but without the limitation on record
locks per table). Everyone can use them freely.
But mind that 'transactions' on desktop databases like Advantage Local
Server and DBISAM aren't real transactions because no desktop database
system can offer crash recovery under all circumstances since every
workstation is directly writing to the database files. So this can
never compete with the real transactions that Advantage Database
Server offers.
Jan
Advantage and DBISAM are both excellent products. I prefer DBISAM: it is
really fast, it optimizes SQL statements pretty good, and, most important
for me, you don't need any DLL or something similar. Everything is in your
.EXE. Oh, and the in memory tables, the repair and compress methods, the
language selection etc. are very handy.
Ralf
According to the DBISAM manual:
_________________________________________
A transaction in DBISAM is buffered, which means that all updates that
take place during a transaction are cached in memory on the local
workstation and are not physically applied to the tables involved in
the transaction until the transaction is committed. If the transaction
is rolled back, then the updates are discarded.
_________________________________________
So, this isn't correct.
_________________________________________________________
Luiz Marques s...@nospam.stg.com.br
[Remove nospam]
Starglider Systems
_________________________________________________________
<< So, this isn't correct. >>
Actually I think it's only fair to also include the text right after that in
the manual:
"This allows for a fair degree of stability in the case of a power failure
on the local workstation, however it will not prevent a problem if a power
failure happens to occur while the commit itself is taking place. Under such
circumstances it's very likely that physical and/or logical corruption of
the tables involved in the transaction could take place."
Just trying to make sure that no one gets the wrong idea. <g>