From: "Rich Mycroft" Subject: Re: Database Load Balancing? Date: 2000/07/07 Message-ID: #1/1 References: <11bd4f90.8e0d58ba@usw-ex0108-063.remarq.com> <20000707.5220800@p200.nodomain> X-Priority: 3 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Trace: newsfeed.slurp.net 962971418 209.144.155.147 (Fri, 07 Jul 2000 07:03:38 CDT) X-MSMail-Priority: Normal NNTP-Posting-Date: Fri, 07 Jul 2000 07:03:38 CDT Newsgroups: comp.databases.oracle.server Another approach is to partition the tables across separate physical db's and then link them. Problem I've seen, at least with SQL Server, is that linked dbs themselves suck wind. My usual approach is to have a very beefy db server, or split the db in ways that are logical collections across multiple boxes so referrential integrity isn't shot to pieces. A lot of times the 'look up' tables are pretty static (when did you hear of us adding a new state to the collection constituted by U.S. ?) so those can exist in multiple db's on different machines without being a huge problem. This has to be done pretty carefully though. On the Java side of life there app servers which do a pretty good job of load balancing - then take all of the app code off of the db server. Your db server should really only be doing db work - don't have it serving up web pages, doing mail, file serving, etc. You get the point. Rich Mycroft "Jerry Gitomer" wrote in message news:20000707.5220800@p200.nodomain... Well if they aren't concerned about data integrity you could ... Your Systems Administrators don't know zilch about how a high performance RDBMS works. Oracle tends to be disk intensive, not processor intensive. That being the case, the way to get better performance is to increase the number of disk spindles and to split data, indexes, redo logs, archives, etc., etc. across as many disk spindles as you can afford. You don't have to go to the extremes that the vendors do for the TPC benchmarks (boy, I would really like to have one of those system with 90+ spindles), but the more disk spindles the merrier. The next thing to do is put as much RAM as you can on the server. These two steps will give you a system that can fly provided that your database is configured properly and - more important than all other factors combined - the applications are properly written and optimized. >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 7/6/00, 12:22:18 PM, Van Messner wrote regarding Database Load Balancing?: > The sysadmins told me they'd like a setup where multiple > copies of an identical database would be accessed depending on > which copy currently had the lightest load. > I've heard of load balancing on application servers but not on > multiple database servers. Neither replication nor parallel > server would seem to provide what the sysadmins want. > Does Oracle have a multiple database solution such as they > describe? > Van > ----------------------------------------------------------- > Got questions? Get answers over the phone at Keen.com. > Up to 100 minutes free! > http://www.keen.com