Evening all, hoping you could provide me with some pointers. I've come accross a MSSQL 2000 database suffering from read performance issues, writes spike now and again but are generally okay. The thing thats puzzled me is the disk configuration is RAID 5+1 (or 51!) i've never seen that sort of setup before.
I'm aware that there are issues with badly written TSQL throughout the db which are causing some of the read issue but i can't help but think that the disks would be better configured using RAID 5 for the data and 0+1 for logs opposed to using just this one 5+1 configuration.
I'd assume as with RAID 5 that reading data wouldn't be an issue with RAID 5+1? Or am i wrong? Is there that bigger overhead to cause these read issues?
(edit - i'm going to be on msn most of the night so if you fancy a chat about it i'd be more than happy to!!!!
- see my profile for msn addy)
I'm aware that there are issues with badly written TSQL throughout the db which are causing some of the read issue but i can't help but think that the disks would be better configured using RAID 5 for the data and 0+1 for logs opposed to using just this one 5+1 configuration.
I'd assume as with RAID 5 that reading data wouldn't be an issue with RAID 5+1? Or am i wrong? Is there that bigger overhead to cause these read issues?
(edit - i'm going to be on msn most of the night so if you fancy a chat about it i'd be more than happy to!!!!
- see my profile for msn addy)
Last edited: