Received: from www.base2inc.com (IDENT:root@www.base2inc.com [204.117.190.140]) by hub.org (8.9.2/8.9.1) with ESMTP id IAA29072 for ; Mon, 22 Mar 1999 08:26:14 -0500 (EST) (envelope-from fmorton@base2inc.com) Received: from tesla (tesla.base2inc.com [206.229.85.131]) by www.base2inc.com (8.8.7/8.8.7) with SMTP id IAA13742 for ; Mon, 22 Mar 1999 08:28:26 -0500 Message-ID: <003c01be7469$23fb6a60$8355e5ce@base2inc.com> Reply-To: "Frank Morton" From: "Frank Morton" To: Subject: Other JDBC Performance Question Date: Mon, 22 Mar 1999 08:37:33 -0500 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0810.800 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 I am using JDBC quite happily and thank you Peter. I have a case where the database is pretty small and the quickest response possible is more important than usual. The whole database is about 2mb or so with lots of different record key combinations. I notice that, even using psql, that each time I do a query, even the same query, the disk is accessed. What I would really like is to somehow force the database to be RAM resident, but still access it using SQL. I am about to write some code to load the whole thing up into RAM and accessing it some special way without SQL, but it really isn't what I want to do. Is there any way to force the database to be RAM resident? Either with this package or something else? I'd appreciate any feedback on how to very quickly access small databases using SQL. Thanks. _________________________________ Frank Morton (fmorton@base2inc.com) Voice: (317) 876-3355 FAX: (317) 876-3398 Home: (317) 574-0815