but can you argue that if it's pretty much sequential write, it will be nicely cached and written as full stripe write with even less write penalty ?
Hi,  Usually when you have a OLTP database, best practice was to have separate spindles for DATA and REDO. I use to do this with "the old fashion" RAID GROUP and MetaLUNs.One for DATA one for REDO aka 2 or more separate disks.  EMC says "Use one pool instead of raid group" well why not.. if performance is not the main subject [IMAGE].  Now with storage pool, I have only one pool and data/redo is spread on all spindles. So even if i create 1 or more LUN the data will be spread by 1G chunks per raig group defined inside my storage pool...  Does it means that now only one lun [thick or thin] is enough for DATA and REDO ?  I think that separate DATA and REDO on 2 separate lun is always a good thing in order to have more granularity in case of performance problems [LUN Migration] but i wish to have a clearly status/feedback.  Another question : I have heard that rebalancing data when you add disk in an existing storage pool is forecast for Q2 / Q3 for VNX BUT what about CX4 ?
Best Practice for Database / Storage Pool