QUESTION POSED ON: 08 December 2006 There is one point on my mind and I would like to have your opinion on it. The area of concern is ASM diskgroup layout. We have a data warehouse of over 3TB and there are about seven data marts, which make up for most of this data. Now the question is, should we create separate disk groups for each of the data marts or should we create one big disk group and throw all the data in it? I have been going through some documents/technical papers and the recommendation is to set up as few disk groups as possible and not separate indexes and MVs into their own disk groups. I wonder if this recommendation is only true for an OLTP environment? Also consider the case where in case there is a problem with one specific large table within a mart, if we were to put all marts in one disk group, wouldn't it have a cascading effect and overall system performance would be degraded?
>
EXPERT RESPONSE
Personally, I like to create separate disk groups for separate instances. This way, I/O from one database does not impact another database. Additionally, data growth in one database won't impact data growth of another. But this may mean that you need more physical disk units to accomplish this.
Search and Browse the Expert Answer Center Search and browse more than 25,000 question and
answer pairs from more than 250 TechTarget industry experts.
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.