Mimer JDBC Overview
Category: JDBC

JDBC is a standardized interface for accessing relational databases from the Java programming language. JDBC™ is short for Java Database Connectivity.

Many companies work together to define new and updated versions of the JDBC specification. Three versions have been defined this far, called JDBC1, JDBC2, and subsequently JDBC3.

This article will give you an overview of JDBC from a Mimer SQL perspective.


The Java environment, called Java 2, currently comes in three different sizes:

For these environments there are corresponding JDBC drivers. These drivers have varying footprint and functionality to suit the environment.

A "normal" JDBC driver implements functionality called JDBC Core. This type of driver is used in the Standard edition environment.

In the enterprise environment more functionality is added to the JDBC driver with something called standard extensions. There are currently four standard extensions defined:

In the enterprise environment application servers are used to access the database. With the use of the standard extensions it is possible, for example, to make consistent updates to distributed databases by using the standard extension for Distributed Transactions. When building applications for application servers in the J2EE environment objects called Enterprise JavaBeans are created. The programmer can focus on application logic, as, for example, transaction handling is provided automatically by the application server.

In the other end of the spectrum we have Java 2 Micro Edition and JDBC for environments where memory and/or resources are scarce. In these environments the footprint of the JDBC software is critical. The JDBC driver has less functionality and cannot use anything but the limited utility classes that are available.

Mimer SQL support for JDBC

The Mimer SQL product line for JDBC is one of the most comprehensive in the industry. Mimer JDBC has support for all the Java 2 environments, from tiny mobile phones running the Java 2 Micro Edition to large enterprise application servers using the Java 2 Enterprise Edition.

In all these environments the JDBC driver has excellent performance characteristics and small footprint. All JDBC drivers are written completely in Java, so-called type 4 drivers. This makes installation and integration particularly smooth.

Enterprise solutions with Mimer JDBC

Mimer SQL is the ideal solution for integration with J2EE application servers. Mimer SQL has native support for 3 of the 4 JDBC standard extensions. Only the database server vendor can provide the three standard extensions for Java Naming, Connection Pooling and Distributed Transactions. Rowsets, however, can be made independent of the database server used.

This support in conjunction with powerful features such as Unicode support and the industries most advanced sorting facilities makes Mimer SQL the ideal solution for the Java developer. With Mimer SQL it is possible to use a wide range of available platforms. Combine this with the standard SQL provided by the Mimer SQL Server and you have a solution with outstanding portability features.

The life cycle cost for a system based on Mimer SQL and Java is the most attractive available today. Here are some of the reasons for this:
  • Low development costs:

    • Simple installation.

    • Free development licenses.

    • Tools integration. You can use your favorite Java tools with Mimer SQL. This allows you to reuse existing knowledge within your organization.

    • Completely standard interfaces and database access language.

    • Rich functionality allowing you to develop more robust applications faster.

    • Integration with existing system with the use of distributed transaction technology.

  • Low deployment costs

    • Support for packaging your application with Mimer SQL.

    • Easy setup of database and backup scripts.

    • Mimerís performance allows you to choose a smaller machine for the same job as competing resource intensive products.

  • Low runtime costs

    • The Mimer SQL system is virtually self-tuning once it is put into production. The system has very few, and simple, tuning parameters.

    • No supervision of database server needed.

    • The "Install and forget"-concept of Mimer SQL is truly amazing.

    • Online backups

    • Automatic reorganization. No downtime for any routine maintenance tasks.

  • Low maintenance costs

    • Easy to add new functionality to an existing production system. The reason for this is that there are no locking conflicts to take into consideration.

    • Many of the low-cost development options are applicable here as well!

The Mimer SQL product has been proven in the most demanding production environments.

Our customers love the product. We think you will too!

Company solutions with Mimer JDBC

The second Java environment is the Java 2 Standard Edition (J2SE). This is the typical Java environment used for applications developed in Java. J2SE provides the essential compiler, tools, runtimes, and APIs for writing, deploying, and running applets and applications in the Java programming language.

In this environment Mimer SQL uses the same JDBC driver as in the enterprise edition, but typically the standard extensions described previously are not used.

In this environment performance and functionality of the driver is important. The Mimer SQL JDBC driver has support for a wide range of features that make it the ideal choice for Java developers:

  • Functionality

    • Scrolling

    • Full range of data types

    • Prepared statements

    • Streams support

    • Cursor names

    • Full Unicode and collation support

    • Callable statements

    • Meta data support

    • and much moreÖ

  • Performance

    • Optimized client/server protocol

    • Support for batched operations. I.e. it is possible to perform several tasks with one roundtrip to the server.

    • The JDBC driver performs bulk fetch of data from the server, thus minimizing communication with the server.

    • Efficient handling of Java objects inside the driver to optimize runtime performance and memory usage.

    • The JDBC client benefits from all the Mimer SQL database serverís performance characteristics.

Due to the fact that the same driver is used as in the Enterprise edition most product arguments are the same for the standard and enterprise edition!

Small footprint solutions with Mimer JDBC

There are several flavours of small footprint Java environments. There are different Mimer SQL JDBC drivers for these environments.

In order to understand the need for different environments and drivers we first have to look at the Java 2 Micro Edition environments.

Connected Device Configuration (CDC)
The Connected Device Configuration is a standards-based framework for building and delivering mobile applications that can be shared across a range of network-connected personal mobile devices. In combination with the J2ME Foundation Profile, which is a set of Java interfaces that supports resource-constrained devices, a complete J2ME application environment for consumer products and embedded devices is provided.

In this environment Mimer JDBC allows database applications to be developed. The Mimer JDBC driver is the first product in the world to follow the JDBC J2ME specification.

This Mimer JDBC driver can be used to communicate with Mimer SQL Engine database servers on central computers or with Mimer SQL Mobile database servers located on, for example, a handheld device. It is thus possible to write applications that work with data located on virtually any type of device. The Mimer JDBC driver uses TCP/IP to communicate with the database server. This means that many different underlying mechanisms such as Bluetooth, wireless LAN, and others, may be used to access the database server.

To develop graphical applications the J2ME Personal Profile is used, which is a superset of the Foundation Profile.

Connected Limited Device Configuration (CLDC)
For environments with even less memory and CPU resources yet another Java architecture is used.

CLDC is the foundation for the Java runtime environment targeted at small, resource-constrained devices, such as mobile phones, pagers, and mainstream personal digital assistants. CLDC, combined with the Mobile Information Device Profile (MIDP), is the Java runtime environment for today's resource-constrained mobile information devices such as phones and entry level PDAs.

In these environments much of the usual functionality found in Java has been ruled out in order to conserve memory. For example, floating point data types are not supported. In addition a special java interpreter called a K Virtual Machine (KVM) is used, which has a smaller footprint than the typical Java Virtual Machine (JVM).

The Mimer JDBC driver for this environment has been adapted to work with the KVM and the sparse runtime environment available. The driver allows, for example, an application on a mobile phone to connect to a database server and retrieve and update data on the remote machine. JDBC drivers are typically not part of this environment and Mimer SQL JDBC drivers are thus extending the capabilities and the functionality of applications in this domain.

When packaging an application with the Mimer JDBC driver in this environment only the parts of the driver actually used by the application are needed. Therefore footprint is decided by what parts of the drivers the application actually use. Sizes between 30k Ė 80k are typical.


This document has described the different Java environments that exists today and how Mimer SQLís database drivers fit into these environments.

Mimer JDBC has a complete range of functionality and support for the smallest devices to the high-end systems and application servers. Mimer JDBC delivers outstanding performance and small footprint for each of these environments. The fact that the driver is written completely in Java makes integration seamless in all environments.


For details, see our articles about Mimer JDBC and Mimer SQL Mobile at the Howto page.

Download our Mimer JDBC drivers at the Download page.

Read more about JDBC at Sun's JDBC product page.

Last updated: 2003-09-09


Powered by Mimer SQL

Powered by Mimer SQL