fragmenting tables with RAID1

Has anyone had any experiences, good or bad, using table fragmentation in combination with RAID1 for their dbspaces? I like the idea of being able to intelligently distribute the data by expression across disks, and the safety of mirroring, but I'm afraid it's going to be slow. We're using it for web applications and are more interested it read performance than writes. I'm not planning on using PDQ for the apps because of the number of users. Thanks in advance, John Stephenson - Presbyterian Church (USA) Database Administrator Phone (502) 569-5442 Fax (502) 569-5163 EMail jstephen@ctr.pcusa.org

I do a lot of upgrades to clients across the country. I almost always suggest using striping and mirrors. The only caveat is that you need quite a few disks to allow the data to be distributed evenly. We ran tests and found that this gave quite a performance increase. It has a side benefit. You don't have to worry about separating the indexes from the data. This is the way we use to do it. It worked great but was an administrative nightmare. Harry Johnson Keene Information Systems, Inc. In article <881jks$26l$1@news.xmission.com>, "John Stephenson" <JStephen@ctr.pcusa.org> wrote: > > Has anyone had any experiences, good or bad, using table fragmentation in > combination with RAID1 for their dbspaces? > > I like the idea of being able to intelligently distribute the data by > expression across disks, and the safety of mirroring, but I'm afraid it's > going to be slow. > > We're using it for web applications and are more interested it read > performance than writes. I'm not planning on using PDQ for the apps because > of the number of users. > > Thanks in advance, > > John Stephenson - Presbyterian Church (USA) > Database Administrator > > Phone (502) 569-5442 > Fax (502) 569-5163 > EMail jstephen@ctr.pcusa.org > > Sent via Deja.com http://www.deja.com/ Before you buy.