SylvJumaga
0 pts. | Dec 22 2005 5:26PM GMT
I’m sorry that I wasn’t clearer in my original message.
All four of the original arrays are RAID 5. The new array I am installing will also be RAID 5.
I would never consider running a production SAP database on volumes that didn’t have redundancy! The RAID 5 has saved my behind more than once.
Sylv
Jolora
0 pts. | Dec 22 2005 5:33PM GMT
I agree with the last post. Security and Data integrity need to be your first concerns.
Also, it seems a little late to be asking/thinking about this now. Better late than never, but…
SylvJumaga
0 pts. | Dec 22 2005 5:38PM GMT
Please rest assured that data integrity has been taken care of.
My question remains - What, in your opinion, would be the optimal way to set up the database on the new blank array?
JodyIV
0 pts. | Dec 22 2005 6:02PM GMT
If the four arrays are of equal size and the existing files will each fit on one of the four arrays, put one file on each array either use drive letters or mountpoints. I would recommend against making the array appear as one drive. If you let one file grow too large, what will happen when its time to upgrade again? You will be looking to move a very large file and would be forced to continue building large drive arrays to keep up with one file. I work with several 1TB plus SQL databases and handle the sizes by creating only 100GB mountpoints and placing 1 file on each mountpoint. We use mountpoints to keep from running out of drive letters. Each 100GB drive gets mounted to its own folder, such as E:Data1, E:Data2.
This will also allow SQL to perform better by spreading IO over serveral drives and files, instead of just endloading one file.
SylvJumaga
0 pts. | Jan 2 2006 10:31AM GMT
Thank you very much, JodyIV, that is exactly the sort of input I was looking for!
Sylv






