From derby-user-return-5537-apmail-db-derby-user-archive=db.apache.org@db.apache.org Fri Nov 10 00:46:18 2006 Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 82254 invoked from network); 10 Nov 2006 00:46:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Nov 2006 00:46:17 -0000 Received: (qmail 52016 invoked by uid 500); 10 Nov 2006 00:46:27 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 51917 invoked by uid 500); 10 Nov 2006 00:46:26 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 51905 invoked by uid 99); 10 Nov 2006 00:46:26 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Nov 2006 16:46:26 -0800 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [32.97.182.144] (HELO e4.ny.us.ibm.com) (32.97.182.144) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Nov 2006 16:46:11 -0800 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e4.ny.us.ibm.com (8.13.8/8.12.11) with ESMTP id kAA0jnUK020508 for ; Thu, 9 Nov 2006 19:45:49 -0500 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with ESMTP id kAA0jnGq281284 for ; Thu, 9 Nov 2006 19:45:49 -0500 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id kAA0jnoa025501 for ; Thu, 9 Nov 2006 19:45:49 -0500 Received: from [127.0.0.1] (IBM-IKEJ04B1IMA.usca.ibm.com [9.72.133.55]) by d01av03.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id kAA0jlPF025436 for ; Thu, 9 Nov 2006 19:45:48 -0500 Message-ID: <4553CBB7.8090406@sbcglobal.net> Date: Thu, 09 Nov 2006 16:45:43 -0800 From: Mike Matrigali Reply-To: mikem_app@sbcglobal.net User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derby Discussion Subject: Re: maximum file size References: <4553A7E5.8060204@alice.it> In-Reply-To: <4553A7E5.8060204@alice.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org no, derby is limited by the file size limits of your os/jvm. Derby itself can support files bigger than 4gig, but only if the OS/jvm supports it. Currently each table is limited to a single file. redcloud wrote: > Hi! I need to build a SQL table containing 1000000000 (!!!) rows. But i > filled up a table with 20000000 rows (file size of table 4GB) and my > filesystem denied to go on filling up the table. My question is: can > derby db build "infinitive" size table by chunking in multiple files? > >