Not long ago, I suddenly saw a colleague still using SP _ to start the stored procedure on SQL Server. So I gave him the msdn link, which is a typical example.
A long time ago, I helped a company with a stored procedure. It was said that it would take many seconds to execute that stored procedure, and that stored procedure was written in a temporary table using an endless loop, then, you can use a complex query statement in the temporary table to query an item until a certain number can be found.
I still remember that in a project last year, the design of the storage process did not consider the lock table issue, and there were some problems in the middle.
Maybe the first problem is that I am nitpicking. The second problem is that I suggest changing the data structure.
However, the database efficiency issue should be considered. This is not just an SQL Server issue.
For example, locking, transaction, and so on can not fully meet the requirements of the database itself, but need to do some work.
There are a lot of books and articles on SQL Server tuning. However, general database designers can understand SQL. Since SQL is a language, he has his design skills and design methods.
I think the following three books can solve the efficiency problems of most SQL Server 2000.
Improving. NET application performance and scalability, an article in Microsoft's patterns & Practices Series
A book from SQL Performance Tuning and Addison Wesley
Inside Microsoft SQL Server 2000, MS Press
