:[EMAIL PROTECTED]]
Sent: Wednesday, March 14, 2001 4:28 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: use one database or many databases
I've run into a situation where i need to split an enormous database (only say a
million rows but oh so long possibly many K)
Using JDBC and pre
I've run into a situation where i need to split an enormous database (only say a
million rows but oh so long possibly many K)
Using JDBC and prepared statements this could be facilitated if we could have the
driver implement a setSQL(int x, "--text--") function which could replace a '?'
placeh
Yes, but I'm really lazy and changing one connect string is easier than going through
200,000 lines of code and changing table names. ;)
That's a good spin on it. Thanks.
--James
---
>From your message of Wed, 14 Mar 2001 14:09:30 -0600:
>Or, you could use one database, a
Or, you could use one database, and lookup the clients table names, and
use a merge table for reports.
James Blackwell wrote:
>
> I have a similiar situation where I've got a huge database that maintains data for
>quite a few clients. Queries have gotten extremely sluggish.
>
> What I'm worki
I have a similiar situation where I've got a huge database that maintains data for
quite a few clients. Queries have gotten extremely sluggish.
What I'm working on right now is to have a control database with a single table that
contains a unique identifier for each client and a database name.
If all the data will be used by the same application then I would suggest
that you stick with a single database.
Cal
http://www.calevans.com
-Original Message-
From: abdelhamid bettache [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 14, 2001 8:11 AM
To: [EMAIL PROTECTED]
Subject: use
