Q
Problem solve Get help with specific problems with your technologies, process and projects.

How many disk groups for our data marts?

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?

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?
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.
This was last published in December 2006

Dig Deeper on Oracle database design and architecture

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close