An approach for large systems design is to spend little time considering performance during the development and set aside project time for performance testing and tuning. This strategy frees the developers from having to consider performance in every aspect of their programming, and gives them the incentive to code more logic in their queries. This strategy makes for faster development time, and more logic in the queries means more opportunities for tuning.
If you choose to make performance decisions during the design phase, each decision should be backed by solid evidence, and not assumptions. You can create test tables, generate some test data, and write some small programs to simulate a performance situation and test your assumptions about how the database behaves. The feedback from these tests provides data to help you design your system for optimum performance. Reports can then be generated and reviewed by stakeholders.
Tools that you can use for testing statements, design ideas, or program processes include, but are not limited to, the following:
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|