SQL Server 2005 can write a stored procedure with .NET language, in small and medium applications, use stored procedure package application logic to a nice choice.
The advantages of using the stored procedure package application logic are as follows:
1. DBA Developer division is clear. Code between code modular. Reduce the database operator and programmer's error. 2, database security; you can set the connection string account only access to the stored procedure, uninterrupted. Such data integrity is also guaranteed. 3, the stored procedure is compiled, the execution is fast. 4, the level of the transaction, the stored procedure level transaction, ADO.NET level transaction comparison. consistency. 5, reduce network traffic. A manner that requires a few rows of Transact-SQL code can be implemented by a separate statement of a procedure code without the need to send a digital line code in the network.
The disadvantage of using the stored procedure package application logic is as follows: 1, the programming language SQL function is poor (excluding SQL 2005) 2, is not enough integration with the programming environment (excluding SQL 2005) 3, portability (different databases) 4, database server pressure Big
It is like the current version of the 9CBS Forum, which is encapsulated during the stored procedure. A more distressed feeling is that the database server is too large. The cost of purchasing higher performance database server is too large. To this end, in the next generation of technical community architecture design, the application logic layer is specifically independently. In the stored procedure here, some adjustments will be made. No longer completely used stored procedure package application logic.
In fact, this issue is very common, many places can be seen, such as 9CBS below:
Http://search.9cbs.net/expert/topic/2437/2437130.xmlhttp://search.9cbs.net/expert/topic/2201/2201278.xmlhttp://search.9cbs.net/expert/topic/ 1980 / 1980958.xml
