Re: Multiple Databases vs a Few
From: Uri Dimant (urid_at_iscar.co.il)
Date: 10/25/04
- Next message: Russell: "Show "Results in Text""
- Previous message: Keith Kratochvil: "Re: Restoring a db from an OS file"
- In reply to: Brian: "Multiple Databases vs a Few"
- Next in thread: Bhanu: "Re: Multiple Databases vs a Few"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 25 Oct 2004 15:50:39 +0200
Brian
There are no reasons to create a database for each client. I think you are
going to build a new model of the database , only you do know a business
requrements.
Visit at www.sql-server_performance.com and you will find a really good
stuff there.
"Brian" <brian@nospam.com> wrote in message
news:%23k$J8cpuEHA.3808@TK2MSFTNGP10.phx.gbl...
> I started work a new company recently and they provide a web based tool to
> companies. The database model is in rough shape -- when a new client
comes
> on they simply create a new database for each client. Right now they have
> roughly 400+ databases split over two database servers.
>
> I am suggesting they bring that # down to a couple. I think managing 400
> connections to a variety of databases might be a performance concern. I
> would also think that in terms of Stored Procs it must be using more
> resources -- instead of optimizing 1 it has to optimize the same 1, 400
> times.
>
> Im guessing on those above --- does anyone know the postive and negatives
in
> doing this, or know of any article discussing this topic.
>
> Thanks
>
>
- Next message: Russell: "Show "Results in Text""
- Previous message: Keith Kratochvil: "Re: Restoring a db from an OS file"
- In reply to: Brian: "Multiple Databases vs a Few"
- Next in thread: Bhanu: "Re: Multiple Databases vs a Few"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|