Hi Martijn,

> This sounds like the "forced writes" attribute of your database
> is "off".

We checked that already. It's not that.

The import is running again right now. When we started the db file was
1.8GB and 40GB free on the disk. At some point, there is almost no
disk space left, but the file is still 1.8GB. Then we stopped the
service (connections all closed) and the DB file size went up to 35GB.

Therefore we look for a solution, to monitor how the DB file is
growing without stopping our import service.

cu Christian