db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Hansson <peterhansson...@yahoo.com>
Subject Re: Very, very large .dat files
Date Tue, 05 Dec 2017 12:59:21 GMT

I guess the question is if Apache Derby supports table partitioning (the 
term used in Oracle RDBMS).  I understand it doesn't.

This means that if I have an incredible large Derby table then that will 
mean an incredible large single .dat file too. (a table is always stored 
in a single .dat file, right?)

Any suggestions? Any props that may control this?

On 05-Dec-17 13:28, Peter Hansson wrote:
> We've seen .dat files  in seg0 directory grow to several hundreds of 
> gigabytes. While everything works ok such a file becomes unmanageable 
> from an OS point of view. Is there a way to control when Derby starts 
> a new conglomerate?  ... so that there are more .dat files but each of 
> them of less size ?
> Thanks.

View raw message