On 01/24/2012 06:21 AM, Xabier Elkano wrote:
> El 24/01/12 11:47, Marcello Romani escribió:
>> I'm just thinking out loud, but I don't see how having a catalog for
>> each client can help you scale, since you can't put them on different db
>> servers. You'd probably have a higher ROI by upgrading the DBMS hardware
>> and/or migrating to postgres and/or throwing some (consultancy) money at
>> tuning.
>>
>> Just my 2 cents.
> Why not? If I want I can put each catalog on different db servers, each
> catalog has its own db config. But this is not the idea, I want to put
> all catalogs on the same db server but trying to keep tables as small as
> possible to reduce IOs on db server, because is the server bottleneck
> now. I can upgrade my server hardware, putting more memory or cpu, but
> my problem is on disks handling these table sizes.

What my company does is run multiple Directors each with its own catalog
DB.  The catalog DBs share the same DB server though (running PostgreSQL).


-- 
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric AT caerllewys DOT net   alaric AT metrocast DOT net   phil AT 
co.ordinate DOT org
  Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater
                 It's not the years, it's the mileage.

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users