H2 DB Temp File is created on separate drive

[Ron Exxon]

I am using an embedded H2 DB (v2.1.210) in a Windows Server 2016 environment.

I have the database configured to use a jdbc URL with a relative path from a location on the D: drive (jdbc:h2:../data).

I have a query with a large result set that seemed to be hanging. Upon further investigation, i found that a  large temp file was created in the User home dir on the C: drive (C:\Users\xxxx\AppData\Local\Temp\3\h2tmp.xxxxxx.temp.db) and caused the C: drive to run out of space.

Is there a configuration option I can set to control where temp files are created? We absolutely cannot have application files written to the C: drive in this environment.

Appreciate any help you can offer. I have not found anybody else who has encountered this problem.

[Noel Grandin]

You'd have to modify how the java VM chooses where to put temporary files.

There are various ways to do that depending on how you want to control it, but at minimum it would have to apply to that whole java process,

[Ron Exxon]

Thanks! That's exactly what I needed.