It seems that a two socket Dual Core Xeon 3060 processor at about 2.4 GHZ would do the trick CPU wise. It sounds like about 2GB of memory would work but we'd need a little more information to be sure. If those 200K inserts are spread evenly over a week they don't sound that bad and I base that on your given 8GB size for your DB. Disk, assuming you do not run in a SAN environment, will be the surprising factor to your sysadmin. What counts is spindles and you are pretty much limited to 73 GB disks. I recommend RAID 1 or RAID 10 and provide separation for your redo, undo, data, and executables, and OS with a minimum of about 12 disks split over a couple of ultra 320 controllers. This advise assumes that you have a small application with disk performance being the limiting factor in your app. You might be able to size smaller but you would have to give us a lot more information about your application and particularly those few query users. Allan On 6/11/07, Jackie Brock <J.Brock@xxxxxxxxxxxxx> wrote:
Hi, all - We're looking to set up a new database server - the old one is gasping out its last breath. At the same time, we'll be (finally!) upgrading to 10g release2. OS will be RedHat on X86-64. I'm not really a hardware girl, and have been asked by my sysadmin to provide some guidance for memory/processor speed/disk performance. We've got a very small (~8g) database with very little traffic on it- about 1 week out of each month, there are approx 200k inserts (and a few scattered updates/deletes), and a few complex queries against the database. Any suggestions (not necessarily specific boxes - more looking for general metrics) would be appreciated. Thanks! -Jackie Jackie D. Brock Database Specialist - Systems Evaluation CableLabs(r) -- //www.freelists.org/webpage/oracle-l