Q
Manage Learn to apply best practices and optimize your operations.

Implementing partitioning before data warehouse upgrade

I am currently running an 8i data warehouse and considering partitioning a 40-million-row table. The database is also in the process of being upgraded to 10g. Will I encounter any problems or performance degradation if I implement my partition strategy in 8i and then eventually run it in 10g? Also, is there a best practice on when you should use partitioning?

I am currently running an 8i data warehouse and considering partitioning a 40-million-row table. The database is also in the process of being upgraded to 10g. Will I encounter any problems or performance degradation if I implement my partition strategy in 8i and then eventually run it in 10g by the end of the summer? Also, is there a best practice on when you should use partitioning, other than the large volume of data?

Implementing partitioning now should not cause you any problems when you migrate to 10g.

Partitioning is usually used on large tables, both to make maintenance easier and to improve performance. If you have the need to perform maintenance on part of a table, even though it is relatively small, partitioning may make sense then, too.

Dig Deeper on Oracle database installation, upgrades and patches

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