MonetDB

MonetDB is a column-oriented relational database built for analytical queries. It speaks its own wire protocol, MAPI, over a plain TCP socket. AddisDB implements that protocol directly, so no additional software is needed on your machine.

Who it is for

MonetDB suits analytical work on a single machine — aggregations and scans over wide tables where a row store would read far more than it needs. It is a full SQL database with transactions, not a query engine over files, and it is a poor fit for high-concurrency transactional traffic.

Set up the server

1. Note the host and port. MAPI listens on 50000 by default.
2. Note the database name. A MonetDB server can host several, and the daemon routes to them by name.
3. Note the user. monetdb is the built-in administrator on a fresh install, and its password is set when the database is created.
4. Check that the database is released for remote connections — monetdb release <db> — if you are connecting from another machine.

monetdb status
mclient -h localhost -p 50000 -d demo -u monetdb

Connect from AddisDB

1. New Connection → MonetDB. Port prefills to 50000 and username to monetdb.
2. Enter the host, the database name and the password.
3. Test, then Save.

What AddisDB gives you

Queries and the Big Data Console, the schema tree, exports, saved queries and mock data. Introspection reads the sys catalog and filters on MonetDB’s own system flag rather than by schema name — which matters, because user tables live in the sys schema by default, so filtering by name would hide them all.

MonetDB distinguishes a SQL NULL from the four-character string “NULL” on the wire, and AddisDB preserves that distinction rather than collapsing them.