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

Software design considerations for performance

I am developing software for an organization with 2,000 independent units. Should I design one set of tables for all units identified by unit code or for each unit separate tables in different schemas? Which design will give the best performance?

I am developing software for an organization with 2,000 independent units; all 2,000 will be using the same applications like FA, Inventory, etc. The volume differs. The plan is to host the application so that the 2,000 units can access it. To get the best output I would like to know how to design the application. Should I design one set of tables for all units identified by unit code or for each unit separate tables in different schemas? Which design will give the best performance?
For 2,000 independent units, I would recommend one schema for all units. But I would also implement a Virtual Private Database (VPD) so that each unit can only see thier own data. The VPD is sometimes called Fine Grained Access Control (FGAC). For more information, please look at the Oracle documentation.

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