You may need to review the partitioning scheme you’ve selected if you add a new OPS instance to your environment or if you add new database functionality.

When you add a new instance to your OPS environment, you need to look at how that instance operates on existing database tables. If the new instance performs queries on data that is in read-only tables or if it runs an application that has its own set of tables, it won’t impact your existing partitioning design. However, you will need to revisit your partitioning strategy if the new instance does either of the following:

You also will need to reevaluate your partitioning scheme if new application functionality is added to an application and that new functionality changes the read/write access patterns of that application. If the new functions access only read-only tables or new tables, then you won’t need to change your partitioning scheme. However, if the new application functionality causes an OPS instance to access tables that are used in a read/write mode by another instance, then you will have to start over with your application analysis. Once again, you will need to determine the overlap tables and decide upon the appropriate partitioning strategy for them.