I have been familiar with databases for several years. I have a course on Database principles in college. I wrote it after my graduation. ProgramMost databases are also used. However, when I study theory in college, I do not know why. After I work, I only talk about practice (for small systems, I don't need to think too much). Therefore, the combination of theory and practice cannot be very good.
For example, the paradigm, such as deadlock, is so familiar with the theory at school that it has never been used for three years. That's why I don't understand why so many people like to write long stored procedures (I used to think that using stored procedures is hard to understand. Now I know the advantages of the stored procedure, but I still don't understand it as so long, why not implement it in the program .).
Now, the new job is related to this. Multi-user concurrent operations, deadlock issues, query efficiency, and so on all require a deep understanding of the database. You need to start learning what you missed.
I have a general understanding of the database (sqlserver2000) in the past two weeks, but I have not had a deep understanding of the time relationship (such as stored procedures, triggers, user-defined functions, indexes, and so on, I have a brief understanding of the Creation command, but I have not studied it in combination with practice). Now I need to learn it well.
Verify it !!!
