All business systems are maintaining and reading data.

On csdn, I read the article "What does the end of the database age mean?", I do not agree with the author's point of view. My point is as follows:

In the information age, information is data, and data is also information. I don't want to chew on anyone who contains it. My point is as follows: All business systems are maintaining and reading data.

The database management system has been developed for nearly eight years. In summary, 90% of my work has only four SQL statements: Select, insert, update, and delete. The SELECT statement is used most often, because all data and various statistical analysis reports are ultimately intended for VIPs orProgram.

Of course, this is a generalization. Select is a general term for all SQL queries, including composite queries, various statistical analysis reports, and Bi analysis results. Other database design and management work is to better obtain this select result. I call this result a final view, and different users need different views, the View content changes at any time. You may just take a look at it or print it out. It may also be read or processed by a program, such as bank transfers or deposit withdrawals.

The development of the database management system is like the "oil man". Without him, it is actually to maintain and read data.

This year, I am 30 years old and I am thirty years old. The program life is not satisfactory. I will focus on being a database administrator in the future. DBA is my interest and ideal.

After that, I would like to worship you in my later years. The New Year's work went smoothly and everything went well.

 

(The content may be general and monotonous. Add my post to the following to enrich the content)

 

# Post on the 13th floor

 

I did not expect so many people to pay attention to it before I leave work. Thank you for your support. On the first day of the new year, I didn't want to show off the crowd. I just wanted to share my personal opinions and discuss with each other.

Public Opinions and opinions are different from each other. My point of view only shows that database storage, structural design, data access, and performance optimization are the focus of an application system, of course it is not necessarily a relational database, but after all, we use RDBMS and SQL for 99% of our daily work. This is my personal interest and development direction.

My current job is also software development. From this perspective, we should take the enterprise business logic as the center, but at the same time I am also responsible for database design and even most DBA work, there are also many people like me. My development step is to first design the database structure according to the business logic process of the enterprise, then write the intermediate business layer, and finally write the user interface of B/S or C/S. I didn't develop based on the test driver. The database design does not seem to be mentioned in the test-driven development, or it is not the scope of the developer's work.

I have studied the relational database design for large systems such as K3, agile, and oracleebs. 95% of interface operations are not select/insert/update/delete for a single table, there are a lot of enterprise business logic not at the intermediate business layer or applicationsCodeIt is implemented in the stored procedure, SQL function, and Releaser, and usually contains operations on several or even 10 or 20 tables in a database transaction. That's why I got this article.ArticlePoint of View: database storage, structure design, data access, and performance optimization are the focus or center of an application system.

Here is another extended topic. Do the intermediate business layer need to be implemented in the program code, or can it be implemented in the database Stored Procedure/SQL function/Releaser, the answer is never to select only the former. The implementation of the business logic of the stored procedure also has a great performance advantage, but the disadvantage may be that it is difficult to manage and maintain.

Therefore, some intermediate business layers are still included in the database for the design of large systems. If you do not believe it, you can check K3/oracleebs. SAP estimates are no exception, not to mention banking/telecommunications systems, although I have never been in touch with the latter two, who said the database is not important. I once worked on a bomcost computing system. I used the MSSQL Stored Procedure, function, and trigger design to regularly calculate and generate the cost of all Bom. Finally, I used the ACCESS project to directly connect MSSQL to display data, it is not developed in any other language or tool.
Did I talk a bunch of nonsense? ^ _ ^, I went to bed.

 

# Post on the 15th floor

Golden ocean is right. In the final analysis, it is still because the object-oriented database is too immature and there is no widely used commercial object-oriented database. Therefore, 99% of our people use RDBMS, however, those who like object-oriented programming have to use the orm architecture designed by others,

Oracle, DB2, SQL Server, and other database management systems all claim to be able to achieve object-oriented data access. However, in our domestic software development process, the actual application is geometric, less than 1% ?.

I seldom use Java, so it is superficial to me. Java is justProgramming LanguageBut there are many third-party organizations on the market using the ORM framework written in Java. Similarly, C # is also a programming language, and LINQ is also an ORM framework. Programming languages are closely related to database access, but they are completely two concepts.