Managing DB2 Performance Across Linux, Unix, Windows and z/OS
正在加载中...
资料简介：
全英文版本，呵呵，英文不好的正好可以借此学习英文了。不过，确实是个好东西，当年我就是靠这个入门的。
INTRODUCTION
Obtaining optimal performance from your DB2 applications is a multi-faceted exercise. DB2
performance optimization cannot be limited to simply tuning SQL. You need to have an
understanding of how factors such as memory, physical design, and maintenance can
affect performance. If you are a DBA having to manage DB2 on multiple platforms, it is
important that you have an understanding of what needs to be monitored.
This whitepaper will discuss how to identify and resolve the most common areas of
performance bottlenecks in DB2 running on Linux, Unix, Windows (LUW) and z/OS. In
addition this whitepaper will compare/contrast memory architecture, physical design,
maintenance and SQL tuning techniques for applications running in z/OS vs. Linux, Unix
or Windows.
DEFINING PERFORMANCE
The Merriam-Webster Dictionary defines performance as “The fulfillment of a claim,
promise or request.” Performance can mean different things to different companies.
Some companies may define performance as 24x7x365 availability, while others may
have specific transaction throughput requirements or minimum response times. Different
tuning techniques need to be applied to these different scenarios.
MONITORING
In order to tune and maintain a subsystem or instance, one must regularly monitor the
entire DB2 environment. Too many people mistakenly focus all of their efforts on tuning
SQL and do not look at the big picture. Think of your DB2 installation as an ecosystem,
where memory, physical design and SQL transactions all work in conjunction with each
other, and all can have a direct impact on performance. Proper SQL coding is probably
the most critical factor related to performance, but it is very important to understand that
the best written SQL statements will not perform properly if there are inadequate
memory allocations or a poor physical database design.
INTRODUCTION
Obtaining optimal performance from your DB2 applications is a multi-faceted exercise. DB2
performance optimization cannot be limited to simply tuning SQL. You need to have an
understanding of how factors such as memory, physical design, and maintenance can
affect performance. If you are a DBA having to manage DB2 on multiple platforms, it is
important that you have an understanding of what needs to be monitored.
This whitepaper will discuss how to identify and resolve the most common areas of
performance bottlenecks in DB2 running on Linux, Unix, Windows (LUW) and z/OS. In
addition this whitepaper will compare/contrast memory architecture, physical design,
maintenance and SQL tuning techniques for applications running in z/OS vs. Linux, Unix
or Windows.
DEFINING PERFORMANCE
The Merriam-Webster Dictionary defines performance as “The fulfillment of a claim,
promise or request.” Performance can mean different things to different companies.
Some companies may define performance as 24x7x365 availability, while others may
have specific transaction throughput requirements or minimum response times. Different
tuning techniques need to be applied to these different scenarios.
MONITORING
In order to tune and maintain a subsystem or instance, one must regularly monitor the
entire DB2 environment. Too many people mistakenly focus all of their efforts on tuning
SQL and do not look at the big picture. Think of your DB2 installation as an ecosystem,
where memory, physical design and SQL transactions all work in conjunction with each
other, and all can have a direct impact on performance. Proper SQL coding is probably
the most critical factor related to performance, but it is very important to understand that
the best written SQL statements will not perform properly if there are inadequate
memory allocations or a poor physical database design.
2014-11-06
页数22
浏览5868
下载7