Shulou(Shulou.com)05/31 Report--

How to integrate extreme programming technology into SQL Server development, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain in detail for you, people with this need can come to learn, I hope you can gain something.

The central premise of the potential limit is that two ideas are better than one. Two programmers sat side by side, one programming and the other picking block by line. The reason for this is obvious: if the person operating on the keyboard is the driver, then the person next to him is the navigator. None of them is the boss-their status is equal and their roles complement each other. What's shocking about extreme programming is the technology that actually works.

Because of the rewards, extreme programming has gained a foothold in the front-end development circle. It may seem absurd to put two expensive developers on the same machine, but it turns out that's not the case. In extreme programming, most program defects are strangled before they occur; optimizations occur when writing slow code; knowledge exchanges; and teamwork occurs.

In my experience, this phenomenon has not yet penetrated into the development of layers. I noticed that in some teams, one person wrote the stored procedure, the second person wrote the data transfer system (DTS), the third did the architecture, and the fourth person commented on the intermediate device interface. Everyone creates the desired objects in isolation and rarely examines the code. Maybe the designer dictates that Sproc98765 take a specific parameter and return a result; then other members of the team correspond to it. In any serious development organization, code review and re-factoring are an integral part of a project, but for some strange reason, they do not extend to the database.

I don't understand that. Maybe together we fooled the managers into thinking that we already knew everything about the database. Or the price of our service is so high that accountants are gasping for breath at the cost of re-factoring and extreme programming every week.

For example, what are the chances that every result I get is correct in a database of 400 tables and 1600 stored procedures? Even if that happens sometimes, the next time a department or customer needs to know about the newly added columns in a table, I have to revisit countless programs, user-defined functions (UDF), and views-- and this only illustrates a change in the table structure.

If possible, I encourage you to try extreme programming to solve the current problems in SQLServer. For this approach, options include the latest developments in a complex stored procedure, factoring a low-speed program again, and optimizing a view. At least give it a try and let me know how it works for you.

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.