Create an ASP. NET data storage layer (1)

Abstract: Learn how to use SQL Server 2000 and Visual Studio. NET 2003 to create a data storage layer for the DotNetKB ASP. NET solution. Security issues related to SQL Server, IIS, and ASP. NET are also discussed.
Introduction
In ASP. NET application planning and design, we discussed the basic planning and design knowledge of the ASP. NET solution named DotNetKB. This section discusses in detail how to use Microsoft? SQL Server? 2000 and Microsoft Visual Studio? . NET 2003 creates a data storage layer. This includes creating databases (adding tables, indexes, constraints, and relationships) and writing stored procedures for data access. We will also discuss security issues related to SQL Server, Internet Information Server (IIS), and ASP. NET. By the end of this section, we will obtain a fully functional and secure data storage system for the DotNetKB solution.
Create a database graph using Visual Studio. NET 2003
One of the many advantages of Visual Studio. NET 2003 is that users can use it as the main SQL Server editor to complete most tasks. After obtaining the appropriate permissions of the target database server, you can easily use Visual Studio. NET 2003 creates various databases, tables, indexes, constraints, relationships, views, stored procedures, and functions. Visual Studio. NET provides a default database project for you to complete the preceding operations. It also includes a large number of templates for creating tables, triggers, stored procedures, and so on. Finally, because Visual Studio. NET is used as the editing environment for SQL Server, you can also use it to store all SQL Server scripts to Microsoft Visual SourceSafe? . This is very convenient for shared projects and other situations that require long-term maintenance.
Reference user Solution
For the project DotNetKB in this series of articles, I have created more than 30 user schemes to identify the tasks required to support the application described in section 1st of this series of articles. We will use these user schemes to identify the data stored in the table and the Stored Procedure executed at runtime to manage the data. The following is a list of some user solutions. The complete list can be found in the User Scenarios for DotNetKB Project (English.