OpenNMS

OpenNMS is the first enterprise-grade network
management platform developed using the open
source model. The three main functional areas of
OpenNMS are service polling, which monitors
services on the network and reports on their
"service level"; data collection from the remote
systems via SNMP in order to measure the
performance of the network; and a system for event
management and notifications.

Release Notes: This release contains a fix for a cross-site-scripting vulnerability, a potentially incompatible change to the way the Web UI is configured (see the "What's New" link for details), and a number of other bugfixes and small enhancements.

Release Notes: This unstable release contains all of the changes from 1.12.4-1.12.6, as well as a bunch of new development on Linkd, Java 8 support, the ability to run Camel and ActiveMQ in the OpenNMS OSGi container, many ReST-related cleanups for XML and JSON output, plus many other smaller bugfixes and features.

It's pretty obvious you don't understand databases. OpenNMS is targeting an Enterprise Solution. Part of that need is performance. Real databases support stored procedures because they can significantly save on both CPU and disk bandwidth. Use of stored procedures also ensures a consistent API is exposed to would-be developers.

Since you're mandating a request of MySQL plus insisting the use of stored procedures should be abandoned, you should really be looking at alternate solutions since your mandates are wholly incompatible with an Enterprise quality solution.

That's pretty funny. This is like saying we can't can't buy a car until it explodes when you can least afford it. Only after it constantly explodes will you consider buying the vehicle.

Hehehe...too funny. Shesh...just about any DB is going to prove more reliable and robust than MySQL. There is a reason why real DBAs consider MySQL to be trash...because it is. It lacks features, teaches poor SQL coding habits, isn't reliable, scales like crap, so on and so on. Seriously...if you consider MySQL to be a mandatory feature then you absolutely are not looking for an Enterprise Solution. Period.

Unknown at the moment. We are getting ready to release 1.3.0 (before LinuxWorld Expo in August) which adds SNMPv3 support, alarms and JMX monitoring.

We use some stored procedures that MySQL did not support prior to 5, which is one of the reasons the movement to MySQL would be difficult. The OpenNMS Group (http://www.opennms.com) provides commercial support and services for OpenNMS, and they might be able to spec a project for you to support MySQL if the need is immediate.