SummaryThis chapter has dealt with three main topics:
Command objects, and using stored procedures and parameters.
This is an extremely important topic for the ADO programmer, since it's one area where performance can be increased without much effort. With stored procedures you have your SQL code on the server where it can be best optimized, and you have control over the data flowing into and out of those procedures.
This is just one of those issues that never goes away, and it's important to think about performance as you design your ASP applications. It's often very difficult trying to rework code to improve performance, and it's nearly always better to code for performance in the first place. The most important thing about performance is to test, test and test. Only you know what your system actually does, so it's important that you take responsibility for this. One great, and easy, way to test your Web site performance is to use the Web Application Stress tool.
Although a less important topic than the other two, it's still worthy, as it brings ease of use to relational data. It can be used very effectively to create generic routines for nested sets of data. There's one of these routines on the sample Web site.
Although that's the end of the chapter, you'll see related bits cropping up in the next two chapters, as well as throughout the rest of the book. Now comes the time to investigate the interaction between the Web server and the browser in a little more detail. After all, having all that data is not much use unless you let people look at it.