- Keep your transactions as short as possible.
- Partition your tables well .. For instance, Keep the most frequently used data in one table and least frequently in another ..
One of the ways to shorten response time..
- Use Joins instead of using co related or sub queries.
- Always try to update data first and then select it.
The more number of times you will hit the database, the more workload will be on the server.
The more number of times you will hit the database, the more workload will be on the server.
So try to read all data at once.....
- To see relations between existing tables, look into database diagrams.
- Basic clauses of SQL like Group By, Having, Where, and IN etc make the backbone of your knowledge in SQL. Try to read articles and blogs covering basics like the one at sqlblogauthority.com.
- Make sure that the tables in use are NOT messed up with a lot of indexes on them. Keep it logical and as economical as you can.
This will help in preventing deadlocks.
- Specify ALWCPYDTA (*OPTIMIZE) to allow the query optimizer to create temporary copies of data so better performance can be obtained.
- Make sure that the tables in use are NOT messed up with a lot of indexes on them. Keep it logical and as economical as you can.
This will help in preventing deadlocks.
- Specify ALWCPYDTA (*OPTIMIZE) to allow the query optimizer to create temporary copies of data so better performance can be obtained.
- Partition your tables well .. For instance, Keep the most frequently used data in one table and least frequently in another ..
One of the ways to shorten response time..
