Database Design for ASP Model Applications

[Krishna Srinivasan]

Right now I am offering some services on an ASP model that uses a
single database. The tables are normalized to use the unique client ID
when performing a query. Wouldn't it be simpler if I just create a
separate database for each client? This way the overheads in querying
the database are reduced and when termination of the account, I just
drop the database. What is the best design for such applications?

Krishna Srinivasan.

[Red Eye Media - Richard Grove]

Re: Database Design for ASP Model Applications


"Krishna Srinivasan" <krishna@multim ediastudio.com> wrote in message
news:361f42ca.0 402092257.60720 798@posting.goo gle.com...[color=blue]
> Right now I am offering some services on an ASP model that uses a
> single database. The tables are normalized to use the unique client ID
> when performing a query. Wouldn't it be simpler if I just create a
> separate database for each client? This way the overheads in querying
> the database are reduced and when termination of the account, I just
> drop the database. What is the best design for such applications?
>
> Krishna Srinivasan.[/color]


MySQL

[Savut]

Re: Database Design for ASP Model Applications

LOL this is not a answer. Well if you think it's better to do so, well do
it. But in MySQL, the limit are user based, and not database based, as far
as I know. Per user, you can define the limit of usage, like the number of
queries per hour, etc...

Savut

"Red Eye Media - Richard Grove" <info@redeyemed ia.co.uk> wrote in message
news:4028a017$0 $18894$65c69314 @mercury.nildra m.net...[color=blue]
>
> "Krishna Srinivasan" <krishna@multim ediastudio.com> wrote in message
> news:361f42ca.0 402092257.60720 798@posting.goo gle.com...[color=green]
> > Right now I am offering some services on an ASP model that uses a
> > single database. The tables are normalized to use the unique client ID
> > when performing a query. Wouldn't it be simpler if I just create a
> > separate database for each client? This way the overheads in querying
> > the database are reduced and when termination of the account, I just
> > drop the database. What is the best design for such applications?
> >
> > Krishna Srinivasan.[/color]
>
>
> MySQL
>
>[/color]

[®ed Eye Media - ®ichard Grove]

Re: Database Design for ASP Model Applications

[color=blue]
> LOL this is not a answer.[/color]

Works for me ;)
RG

[Jochen Daum]

Re: Database Design for ASP Model Applications

Hi!

On 9 Feb 2004 22:57:08 -0800, krishna@multime diastudio.com (Krishna
Srinivasan) wrote:
[color=blue]
>Right now I am offering some services on an ASP model that uses a
>single database. The tables are normalized to use the unique client ID
>when performing a query. Wouldn't it be simpler if I just create a
>separate database for each client? This way the overheads in querying
>the database are reduced and when termination of the account, I just
>drop the database. What is the best design for such applications?[/color]

Depends how much reporting you want, which is over all users. If a
lot, put it in one database, otherwise in many. Some of your users
might also demand to have a separate database with separate rights, so
it might be constraiend by that.

HTH,

Jochen
--
Jochen Daum - Cabletalk Group Ltd.
PHP DB Edit Toolkit -- PHP scripts for building
database editing interfaces.

http://sourceforge.net/projects/phpdbedittk/

[CountScubula]

Re: Database Design for ASP Model Applications

"Krishna Srinivasan" <krishna@multim ediastudio.com> wrote in message
news:361f42ca.0 402092257.60720 798@posting.goo gle.com...[color=blue]
> Right now I am offering some services on an ASP model that uses a
> single database. The tables are normalized to use the unique client ID
> when performing a query. Wouldn't it be simpler if I just create a
> separate database for each client? This way the overheads in querying
> the database are reduced and when termination of the account, I just
> drop the database. What is the best design for such applications?
>
> Krishna Srinivasan.[/color]

IMHO, Several databases, thus if load of one gets too high, move it to
another box, thus you start out with the ability to scale. Otherwise, you
get locked in, and will have downtime shoud high usage and/or
lots-o-clients.

Also, as a side note, use DNS to point to each database for each client,
this way the front end webservers just connect to a *named* back end server.

Well just my 2 cents.

--
Mike Bradley
http://www.gzentools.com -- free online php tools