From diners to the chef - book review "Oracle Performance Optimization Technology"
Author: kamusmail: kamus@itpub.netdate: 2004-4
In fact, Fenng previously made the book review of this book in the programmer magazine of 9CBS. When I saw the book review, I didn't buy it yet, just downloaded the electronic version of the English. Seeing Chapter 2, I feel a very good book, so I bought a book on China-Pub. This kind of mood is better than the CD that I like myself. It is otherwise available. , Then earn an eye, the horse and tiger have been calculated. Borrowing Fenng for this book, "Read this book, maybe many Oracle 7/8 era DBA will be frustrated: Because they will find that some of the optimization methods and thoughts are actually wrong!". What is it already attracting you with a single sentence, you have to know that it is not your fault once, but after you have this book, you are still wrong for the second time, that is your problem. Quiet, one page reads a book, telling the truth, is difficult. When the average person will start to touch a new book, it is very excited, and full of ambition must finish this book. As a result, it is nothing to see if it is not interested in the middle, but it is often Will you think that this chapter will miss this important link, so he is in the middle of the year, uneasy, and suffocating the years, cleaning the drawer or even the closet, is not a bunch of bought, but did not finish reading book? But fortunately, this book will not.
The beginning of each chapter of this book has several misunderstandings and facts, and the misunderstanding will see a lot of prior to tuning theory and methods, and the fact part is refuteed to this misunderstanding. At the same time, the elaboration of the fact is an important part of this chapter.
The chapter distribution of the book is also a worthwhile place. From the time, it is part of the task that is a DBA facing tuning. The first chapter introduces the method of waiting for events and tracking performance issues. This is the basic theory and basic means of tuning. The next second chapter is the application's optimization, maybe everyone knows, maybe some people don't know, actually optimized 80% of the work is in the application section, which is also difficult as a DBA work. The program is not what we have written. Maybe the prudent design is not involved. Wait until the project is online, it is found that performance issues, this is Many of the domestic projects are too common, what can we do? We need to find the most important place to lead to performance issues. Basically, we are all procedures, we propose programs, may be accepted, may not, because this time it is too late, but as DBA, us It should be done to our own points and should be proposed, even if this time it is impossible to modify this, the next time maybe it will be. Therefore, do not complain that the programmer is poor, that SQL write, because optimization SQL is not a programmer, but we have work, if most programmers write SQL is very poor, then maybe Just indicate a question, that is, you are not a very competent DBA because it is also a duty of DBA for programmer training. It seems to be some exemplary, then we will come back to return to Zhengchuan. If the application cannot be adjusted in all cases, or if it has been unable to adjust, then we will enter the next step, instance, and database optimization, including the optimization of the SGA components, including the optimization of the physical storage structure of the database . Next, some of the other special optimizations, as well as environmental optimization, including parallel, I / O, operating system environment setting, and so on. This book reads the feelings, it is a big feast, every dish is very beautiful and there is no greasy, every dish is worthy of you, you will be careful after you have finished the taste. Just know the practice of all dishes, however, every time when you encounter it to make up, you will still think of such a dish before you have eaten such a dish, you can't stand it again, this time Your impression of this dish is deep, then it is next time. . . When you close your eyes, this rich dinner has emerged in front of your eyes. For every dish, you clearly know how much salt, how much, steamed how long it is fried, then congratulations You have evolved from diners as a chef, which is already a master of the master.
Finally, I still have to send some complaints, although this book is already in turn, it is basically not a ridiculous mistake, but some problems will still be found during the reading. For example, there is a small chapter title is "how to write SQL", when I saw it, I really don't understand, don't you write SQL? Does DBA should write SQL? Continue to see it, I know, oh, what should I don't write, which should avoid what should be avoided when writing SQL. Later I checked the original text, I found that it is how not to write sql. I think if I don't think about the direct translation, then naturally "how to write SQL". If the above is still tolerated, then the following sentence is really a little crying. Still this chapter of How Not to Write SQL, one, "This query is not smart, but for integrity, we must talk about it. Don't be a SELECT statement for all connection conditions for all tables in the FROM clause Conditioning the WHERE clause. "If you say it, you will understand this sentence three times, then I really admire this person. The original is:. This one is no-brainer, but we have to mention it for the sake of completeness Do not build the where clause predicates for a select statement without having all the join conditions for all tables in your from clause First of all, this. The query is not smart? Which query? not smart? It should be obvious "This article is obvious, but for integrity, we must mention", then followed, the translation is directly collapsed, I have seen more than 10 times, and finally I still read the original text of. Means, do not write a WHERE clause that does not contain all the connection conditions of all tables that have occurred in the FROM clause. To be honest, I also translate it too much, but I am not a professional translator, this, huh, huh, I can forgive. A good translation requires Jianda, I hope to see more and higher quality translation works later. May 2004 Kamus
"Oracle Performance Optimization Technology" / Gaja Krishna Vaidyanatha waiting / Zhong Ming and other translation / machinery industry publishing house
