But don't worry about that memory leak. It might not occur with your application.
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.
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)
>Hello SAP list folks --
>
>I have successfully installed SAP DB 7.3 and the 7.4 database tools and
>played around a bit with some data manipulation.
>
>I would like to use SAPDB as our web database of choice -- but my partner
>is concerned about its reliability -- and the amount of dba time/effort
>needed to keep it running. He feels no one is going to pay us to baby sit
>a web database, and reliability (especially in this economy) is extremely
>important. The darn thing should just run.
Hmm ... let's quote the SAPDB Homepage: "# High performance and scalability # Round-the-clock operation"
Please ask you partner _why_ he wants to use MySQL.>If there are success stories out there -- I'd like to hear them. My >partner wants to use MySQL (reliable & fast -- but limited functionality >for example -- no views, no stored procs)...
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'd like to use something more powerful with more features (I'm not crazyI'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.
>about using C as the stored proc language -- but its nice to have views).
>
>So if you all can share your experiences -- as to reliability or the amount
>of DBA load needed to keep it running -- it would be much appreciated.
It's the best DB i could get for my money ($0 :-) )
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
