Derby has problems when you do simultaneous INSERTs and SELECTs on the same table with fast growing tables. See
https://issues.apache.org/jira/browse/DERBY-2991 for details. If this is the case for your application, then make sure that there are no SELECTs while INSERTing data. Am Freitag 29 August 2008 schrieb Dmitri Pissarenko: > Hello! > > I have an application, which has to store following amounts of data: > > 1) There are approx. 20 MB of data per day. > 2) The database should be able to store data of, at least, one week, > i. e. 7 * 20 = 140 MB, at most - data of a quarter, i. e. 30 * 20 * 3 > = 1800 MB. > > The data is imported into Derby and then displayed in form of reports > (based on Crystal Reports). > > 1) I would like to know whether Derby is suitable for such amounts of > data? > > 2) What is the "threshold", maximum amount of data Derby was designed > to cope with? > > Thanks in advance > > Dmitri Pissarenko -- Mit freundlichen Grüßen Kurt Huwig (Vorstand) Telefon 0681 / 3 72 00 36 - 50 http://www.iku-ag.de/ Telefax 0681 / 3 72 00 36 - 59 iKu Systemhaus AG, Altenkesseler Straße 17/Gebäude C1, 66115 Saarbrücken Amtsgericht: Saarbrücken, HRB 13240 Vorstand: Kurt Huwig Aufsichtsratsvorsitzender: Jan Bankstahl GnuPG 1024D/99DD9468 64B1 0C5B 82BC E16E 8940 EB6D 4C32 F908 99DD 9468
