My question: How to learn MySQL "systematically"?
For example, which books should I read? I have studied the following books: "High Performance MySQL", mysql optimization by Jian Chaoyang, innodb storage engine. I personally feel that the first two are to tell readers what they know, and the third one is to tell readers why. There is a gradual relationship between these three books. If there is no accumulation of the first two books and certain work experience, the effect of directly reading the third book is not very good.
Learning database knowledge, or learning mysql in a narrow sense, the learning process is quite tortuous. No one can tell you, as long as you have read a few books and mastered which knowledge is proficient and mastered mysql. The knowledge is very broad, and the knowledge points are scattered. It is not as systematic and straightforward as learning programming languages.
This is where I feel more confused, how can I study systematically?
Now I am reading the official reference manual in English when I have time after work. One is to cultivate the ability to read English technical documents, and the other is to study systematically through the official documents, not just one or two technical documents, one or two technical documents. Cases are such a fragmented way of learning.
The official documentation of mysql is a very systematic and detailed guide.
In addition to reading, you can refer to books written by other people.
Author: Wen Guobing
Link : https://www.zhihu.com/question/21760988/answer/19235639
Source
: Zhihu Edition" is a rare good book, the principles behind any database are basically figured out, and the others are improvements and optimizations made by different manufacturers or organizations;
2. If you don't understand the structure and principles of MySQL questions, you should read books related to optimization. I think it's futile, because you don't understand the principles, how can you talk about optimization? Therefore, two books can be recommended here: "In-depth Understanding of MySQL" (translated by Yang Tao, etc., Charles A Bell, People's Mail Publishing House), "In-depth Understanding of MySQL Core Technology" (O'REILLY Publishing House, China Electric Power Publishing House, Sasha Pachev, Li Fang, etc.) translation);
3. After thoroughly understanding the fundamentals, plus enough practice, you can now read books on optimization, high availability, backup and recovery, clustering, and optimization, such as the "High Performance MySQL" mentioned by the predecessors. "(O'REILLY Press, Electronic Industry Press, Baron Schwartz, waiting for translation by Wang Xiaodong, etc.), "MySQL Performance Tuning and Architecture Design" (Jian Chaoyang), other books such as "Highly Available MySQL - Building a Robust Data Center" (Charles Bell, O'REILLY Publishing House, Electronic Industry Press, waiting for translation by Ning Qing, etc.)... (Additions are welcome)
4. You can study the MySQL source code, internal implementation mechanism and so on in a deeper level. I don't know the direction here either;
5. The knowledge of Linux must be very proficient in the predecessors, so I won't go into details here.
Two posts are posted below,
one is an excerpt from " Famous DBA expert Mr. Feng Chunpei shares his career path ", and the
other is an excerpt from " How to understand the essential qualities and skills of an advanced MySQL DBA ".
From: Mr. Feng Chunpei, a well-known DBA expert, shares his career path
hwayw:
Now some people think that learning oracle is a good way, some people think that learning mysql has a better future, and some people think that nosql is the future database trend, what do you think of this point of view ? What do you think of the controversy over relational and non-relational databases?
biti_rainy:
When I was learning oracle, the oracle database was still widely used, and there were few DBAs, so I was ignorant and entered the right door at the right time. From 2001 to 2006, it was really a golden period for DBAs to learn and grow. At that time, a bunch of influential people emerged. This is not to say that the current oracle DBA skills are worse than those of that time, but it is indeed not a golden age now, because oracle has been widely used. But now this period is a good time to do database services, and we wanted to do it at that time but it was not feasible. In 2006, I recruited a freshman named Jian Chaoyang. Later, I suggested that he focus on learning mysql, and gave him a lot of freedom and plans to help him grow. Later, he wrote a book and grew up on his own. Very fast and very influential in the mysql field. The reason why he was advised to learn mysql at that time was because the overall cost of oracle hardware implementation was very high. Once a minicomputer and SAN storage were used, the oracle cost was actually less than 20% of the total cost. On the one hand, for the company to save costs, on the other hand, I feel that this is the future trend. The big environment gave him this opportunity, but I just made a judgment in advance and guided him. Now due to the development of Internet companies, it seems that nosql is developing rapidly, but this is actually just solving specific problems in specific scenarios. I think it is a false proposition that nosql can replace RDBMS in the next ten years. In fact, the trend of the two is gradually consistent. If nosql wants to be universal, it must have many features of RDBMS. The longer it is, the more similar it is. Google's recently released database, in fact, I see many features and concepts similar to oracles. Conceptually, everyone has nothing new, but the quantitative changes in scale lead to qualitative changes. The easiest way for ordinary users to solve the scale problem is the breakthrough of hardware and network, which is more likely to bring about the development of database applications. Therefore, I advocate that everyone should look at the essence of technology through phenomena, and study the pros and cons behind the characteristics of various technologies, so that they can have their own views. Oracle, mysql, and nosql are all specific forms of data management. They mainly face what customers, what problems they solve, and what value they bring. If we see through these, we will not be drawn by appearances. Of course, I think that after managing the data, it is a very important thing to discover the value of the data.
From: How to understand the necessary literacy and skills of advanced MySQL DBA?
1. The role of important parameters of MYSQL; what are the side effects? Yes key_buffer_size, tmp_table_size, sort_buffer_size, innodb_buffer_size, innodb_log_file_size, innodb_flush_logs_at_trx_commit, max_tmp_tables, and more!
2. You need to be proficient in SHELL; what does the shell refer to specifically, can you give an example of a book, and if you understand this book, even if you are proficient in the shell?
3, PYTHON, PERL understand one. I don't understand, it seems that I have to buy a book and practice slowly.
4. The performance test must be met; if it has not been done, how to do it, what tools to use, and how to see various test data after the test.
5, LINUX skilled operation; what aspects of linux operation include? Can you give some examples?
-
MySQL learning tetralogy
http://yaocoder.blog.51cto.com/2668309/1224685
I have a habit of buying books. First, I go to Douban to see the book rating (I feel that Douban's data is the most objective), so I found these four books The MySQL book, I call it a tetralogy.
Part 1: "SQL Study Guide"
This book is suitable for people who are new to MySQL, especially for engineers who use MySQL. The content of the book is about the standard SQL language, which naturally includes knowledge of other databases, but I found that the author is very biased towards MySQL, and there is a lot of space about MySQL. After reading this book, you will quickly have an overview of MySQL, and the explanation of SQL statements is also very detailed and profound. For engineers who use MySQL, it is almost the same after reading this book.
The second part: "High-performance MySQL"
was the second edition when I knew this book. Bookstores and online merchants were looking for it, but they were all out of stock, which was very disappointing. Until I bought the third edition a while ago, I have read it for a while, but it is estimated that it will take a while to finish reading this kind of big book. I saw the second version in the Douban commentary saying that the translation was not good, but I feel that this version is quite smooth, and I didn't find any ambiguous words. As its name suggests, this book is more about how to improve the performance of MySQL. It is quite practical. It solved several of our problems just after reading it. I feel that this book is more suitable for architects and DBAs to read. To me, it corresponds to vertical scaling in architectural design.
Part 3: "Highly Available MySQL"
"Master/Standby, Read/Write Separation, Clustering" Everyone should be familiar with these concepts. The subtitles of this book are "Building a Robust Data Center", "Master-Slave, Read-Write Separation, Replication, Clustering..." These topics will be covered in the book, and our current data volume cannot reach this level At this stage, I can only study theoretically. I hope that one day the amount of business data will give me the opportunity to practice. It is said that with this amount of data, my life will be worry-free and eager. This book is more suitable for architects, DBAs to read. To me, it corresponds to horizontal scaling in architectural design.
Part 4: "SQL Anti-patterns"
is a book suitable for all types of database design. Unlike the writing patterns of other books, the author will first put forward a point of view that we often use, and then point out its inappropriateness. Then give us a relatively correct point of view (even anti-patterns have their applicable scenarios), this book is suitable for architects and DBAs to read.
-