Experience in Oracle Database 11G & MySQL 5.6 development manual

The wave of big data is surging, and a new information technology revolution is about to begin. "Spring River plumbing duck Xianzhi", as a database practitioner, is particularly profound to me.
However, whether it is Oracle's exadata, MySQL's scale out, or nosql, all have their own application scenarios, there is no difference between advantages and disadvantages
The big data concentration is still largely distributed, depending on the company's finance, technical support, atmosphere, needs, etc,

Let's take a look at February 2013.4The market usage of each database in the month:

 

Next, let's talk about Oracle's acquisition of MySQL. Many people are pessimistic about MySQL, But I think Oracle has invested a lot in MySQL:
1. modularized reconstruction of MySQL code
2. Optimize the development model
3. Excellent MySQL performance optimization experts
4. continuously improve the MySQL Partition Function
5. Rigorous MySQL QA Team
6. Continuous development of InnoDB
7. continuously improve MySQL replication, optimizer, and manageability
Of course, there are many others. This is just the tip of the iceberg. Please be pessimistic.
 
This book is a basic literacy book, focusing on helping readers clarify concepts. Each chapter is a comparison of two database operations. Only by understanding these differences can we achieve seamless operation.
It should be of great help to users who want to migrate data between Oracle and MySQL, or who want to develop applications based on these two database platforms.
For example:
Chapter 1, p131
In this chapter, it clearly states that the schema in Oracle is synonymous with the user.
In MySQL, schema is actually synonymous with database
I think this distinction is particularly important. Creating a database in Oracle is a huge project.
However, in MySQL, you only need to create a database.
Therefore, it is necessary to clarify the differences between the two databases.

Chapter 2, p46
In this chapter, the daily management and basic operations of MySQL monitor are described in detail.
The SQL * Plus of MySQL monitor and Oracle is synonymous, and the author also compares it in the book.

③ This book has a very good architecture
Each chapter in this book is about Oracle, MySQL, and the similarities and differences between the two,
Every small point is not in-depth, simple, and clear.

④ Post exercise after each chapter
This part of settings may not be necessary for people who have already worked.
It may be useful for lecturers, students, and students to place this book in a university class.
It doesn't matter when or when the databases used by the University's database principles are no longer MSSQL but oracle.
Maybe not far away,

Chapter 5 Constraints
The five constraints of the database have always left many beginners confused about the use of the database.
In this chapter, I personally think the author has introduced the restrictions on the use of the two databases.
This kind of introduction is easy to understand and is good at operation.

Chapter 6 Security Model
MySQL security is a little inadequate. Maybe it is the positioning of this book.
This book introduces the development of Oracle and MySQL, but the security of MySQL, I think DBA people should have a deep understanding

 
Of course, there are some translation deficiencies in this book,
For example, Chapter 7 p217 discard views in Oracle databases and here "discard" should not be translated
For example, Chapter 3rd defines the rights of the creator and caller, the "rights" here, and the term "Permissions" in the database"
There are still examples like this, but they will not be listed one by one, but they will not impede reading.