Practical Aspects in Physical Database Design - Automated Physical Database Design and Tuning - page 134

• Provide means to gather, clean, and compress input workloads.

•

Present different tuning options for specific user needs, such as different
tuning models, the ability to pause and restart sessions, or the possibility
to ooad most of the tuning overhead to a test server.

• Generate useful reports that explain and complement the recommended

configurations as well as ecient scripts to deploy the resulting physical
designs.

7.10 Additional Reading
Several ideas described in this chapter can be found in white papers, aca-
demic publications, and topic chapters. 1 , 4 , 6 , 9 Some references discuss in more
detail specific topics, such as workload compression 3 and the physical design
scheduling problem. 2 The reader can consult, for more information, the doc-
umentation of commercial physical design tools, such as the Database Engine
Tuning Advisor in Microsoft SQL Server, 7 the db2advis utility in IBM DB2, 5
and automatic SQL tuning capabilities in Oracle. 8

References
1. Sanjay Agrawal, Surajit Chaudhuri, Lubor Kollar, Arun Marathe, Vivek
Narasayya, and Manoj Syamala. Database Tuning Advisor for Microsoft
SQL Server 2005. In Proceedings of the International Conference on Very
Large Databases (VLDB) , 2004.
2. Nicolas Bruno and Surajit Chaudhuri. Physical design refinement: The
“merge-reduce” approach. ACM Transactions on Database Systems ,
32(4), 2007.
3. Surajit Chaudhuri, Ashish Gupta, and Vivek Narasayya. Compressing
SQL workloads. In Proceedings of the ACM International Conference on
Management of Data (SIGMOD) , 2002.
4. Benoit Dageville, Dinesh Das, Karl Dias, Khaled Yagoub, Mohamed
Zait, and Mohamed Ziauddin. Automatic SQL tuning in Oracle 10g. In
Proceedings of the International Conference on Very Large Databases
(VLDB) , 2004.
5. IBM. The Design Advisor . Available at http://publib.boulder.ibm.com/
infocenter/db2luw/v9r5/topic/com.ibm.db2luw.admin.perf.doc/doc-
/c0005144.html.