I listen to Fenng introduction today to activate this account that has never been used for a long time.
None of him, have a lot of feelings that have been learned in Oracle for a few years.
Also prepared to organize and record, hope to help others
About a few weeks have a netizen asking a netizen in the water:
Seeking: The difference between Oracle and SQL
A alumni answer:
Oracle is just a relational database product, a DBMS. SQL is the operational language of all relational databases. Learn the database, SQL is most important. Every DBMS will extend much less extension standard SQL, provide more features and services, but expand SQL portability is extremely poor, but this jar is Oracle, so it is certainly not too paying attention to it.
Therefore, I naturally have different opinions, summarizing my understanding of this.
1: I guess the difference between Oracle and MSSQL for him 2: SQL, is the most important for developers who initially use the database, if you want further tuning SQL, understand SQL execution plan, general algorithm and database The principle of the optimizer is most important. Knowledge, understand that some things of the database layer have seriously affected SQL execution plan 4: To say to learn a database, really important, true geographical solution architecture and database concept, understand why the database is designed so, then understand backup recovery The principle of TUNING, combined with a large number of practices, verification principles, improve the theory, in turn guided by theory, complement each other, is unable! 5: Further, enter the database architecture and the implementation layer of the database architecture and the basic concept, enter the INTERNAL phase, understand the important function of the database to implement algorithm and processing mechanism, this time management database and optimization database is basically like this It is naturally basically the same as eating clothes, which is elaborated from the perspective of Oracle's understanding. If it is MSSQL, it may usually stop in the Tuning SQL section. You must understand the characteristics of various databases to best take them unless you really want to do a common product that is suitable for running on any database, you still need to understand the characteristics of various databases, you will be able to Better design universal code and understand the general code will lose too much database function
When I read it earlier, it was more than 2 years ago, I once learned Oracle for some levels of understanding, and I also searched it here, I will refer to it today.
