RDM Server - Embedded Client/Server Database
What's New
RDM Server is a powerful, cross-platform, small footprint database designed for server applications with demanding performance requirements. RDM Server meets the needs of competitive businesses and embedded applications by offering a feature rich and scalable data management solution.
RDM Server Overview
RDM Server is Birdstep's response to the growing market demand for handling huge volumes of data
at extreme transaction rates. The database offers a strong foundation for application development
with tools for performance enhancement and database customization. RDM Server continues this
legacy by adding critical features for many users and developers. With the existing features of
complex data management this new version extends the highly configurable database engine with
the following features:
SQL Triggers - In addition to supporting C triggers, RDM Server now also supports SQL Triggers. A SQL trigger is procedural code that is automatically executed in response to an insert, update, or delete event on a database table. The procedural code runs in the same transaction context as it was triggered and is tremendously useful in maintaining the data integrity. Having the power to void a transaction that breaks pre-defined business rules is extremely useful when designing complex database applications. For example, when a new record is added to an employee's table, new records should also be created in the employee vacation and salary tables. The latter two operations are business rules triggered by the creation of the employee. The salary table may have a pre-defined max salary value which can invalidate the creation of the employee if the manager tries to associate a higher salary for the new employee, violating the corporate rules.
SQL Unions - The SQL UNION clause combines the results of two queries into a single resultset of all matching rows. The two queries must have the same number columns and is useful in data warehouse applications where tables aren't perfectly normalized. A simple example would be a database having tables ip_traffic_january and ip_traffic_february that have identical structures but are separated due to performance considerations. The union operation will join the results from the two tables into a single resultset as if the application was viewing a single table. However, because the data is stored in two separate tables, inserts will be executed faster by maintaining smaller independent sets of data in associated index structures.