Thanks guys for the information on how you are using SAPdb, and the reference to the tech ed article.
I am very excited about this product. If there are any others out there with user experience re ease of administration, reliability, etc. I am very interested.
Best wishes!
Bob AckerMead, CO, USA
Robert wrote----->
Hi Bob,
we've used SAPDB as the database backend for web applications in
production
for about 2 years. DBA work necessary is minimal (basically run
software
updates from time to time, add another devspace if the existing ones
are
full) and the tools make these tasks trivial. The database has been
rockstable (not a single failure in months uptime) until we ran into
rather
strange problems with memory leaks (see list archives and use my email
address as a search term) about 2 months ago. We still haven't resolved
the
problem but suspect it's something rather strange with our system setup
or
the way we use the database because the problem has not been reported
by
anyone else. So IMHO, you should run stresstests with sapdb and your
application and if you don't run into any problems use it for
production.
Regards,
Robert
Rich wrote ----->
Bob,
Take a look at the Tech Ed 2002 PDF online at
http://www.sapdb.org/pdf/teched2002.pdf
There is a list of larger organistaions using SAP DB production in that
document.
I'm inclined to agree with Sven regarding MySQL - It's a nice little
database
in itself, but it's no way comparable to SAPDB.
My feeling is that you and your partner should look at the requirements
of the
applciation, and choose based on that. If MySQL does everything you
need, go
with it - but if you need the views, stored procs, transactions, fast
multiuser
acces, scalability, and so on, go with SAPDB (or possibly PostgreSQL).
I don't want to get too off-topic, but take a look at the licensing of
the various
MySQL 4 versions, as well...
As far as baby sitting SAPDB, there's not a lot to be done - just
backups (as
with anything), adding devspaces!
!
if your needs grow, and maybe an
occasional
update of the statistics to help the query optimizer.
If you're partner is looking back over the lists and seeing problems,
that's
pretty normal - the people it's working well for rarely complain :-) I
think
you'll find it's solid in most situations.
skoehler wrote ----->
But don't worry about that memory leak. It might not occur with your
application.
a stresstest is impossible, because he doesn't write the application
first - his application will be very database-specific.
(for example the query language of SAPDB and MySQL differ)
Please ask you partner _why_ he wants to use MySQL.
I don't want to start a flamewar again, but MySQL doesn't support some
features it should have.
1. SubSleects (which might come with 4.x versions ...)
2. ForeignKeys / Referencial Constraints (which won't be supported by
MySQL - even in the future - there's a statement in the docs, that
ForeignKeys are for ?documentation? only)
I'm going to launch a web-application using SAPDB in 2 months, and i'm
looking forward to see it running, because i believe in SAPDB.
It's the best DB i could get for my money ($0 :-) )
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now
