Hibernate ships with detailed support for many^[9] commercial and free relational databases. While most features will work properly without doing so, it’s important to set the hibernate.dialect configuration property to the right subclass of org.hibernate.dialect.Dialect, especially if you want to use features like native or sequence primary key generation or session locking. Choosing a dialect is also a very convenient way of setting up a whole raft of Hibernate configuration parameters you’d otherwise have to deal with individually.

If you don’t see your target database here, check whether support has been added to the latest Hibernate release. Most of the dialects are listed in the SQL Dialects section of the Hibernate reference documentation. If that doesn’t pan out, see if you can find a third-party effort to support the database, or consider starting your own!