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

This article mainly introduces "the installation method of SQL Server2000". In the daily operation, I believe that many people have doubts about the installation method of SQL Server2000. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts about "installation method of SQL Server2000". Next, please follow the editor to study!

1. Server components

SQL Server 2000 consists of two parts: server components and client tools.

1. Content

The server component of SQL Server runs as a Windows service (Windows Services). It is generally believed that SQLServer contains four Windows services (here we focus on OLTP, not OLAP for the time being), which are: MSSqlServer, DTC?Distributed Transaction Coordinator?, SQLServerAgent, and Search Service.

MSSqlServer is the most commonly used service, which provides general functions, such as file management, query processing, data storage, etc.; DTC is a distributed transaction coordinator that supports update operations across two or more servers to ensure transaction integrity; SQLServerAgent is responsible for SQLServer automation, which is needed if SQLServer is required to execute a stored procedure at a specified time Search Service is a full-text query service, which is responsible for full-text retrieval.

two。 The reason why one is divided into four

Now we know that at the core of SQL Server are four server components that run as Windows services. Smart readers may wonder: why do server components run as Windows services? Why do you need to split the complete system into four server components?

● uses the SQL Server server component as a Windows service program mainly because the Windows service program can be used when the user is not logged in.

● divides the core functions of SQL Server into four Windows service programs, mainly considering the following factors: the tasks undertaken by these Windows service programs are functionally divisible, which is a prerequisite; not every application needs to use all the functions provided by the four services, so that users can selectively shut down some services, which can undoubtedly save the resources of the system and the energy spent by users on management. Finally, separate into multiple service programs, you can set operating system-level security policies for each service.

II. Client tools

At the core of SQL Server 2000 are the server components discussed above, but users are not directly exposed to them (although they are really working on them), but client-side tools. The server component is the engine and the client tool is the user interface, and the two complement each other.

Let's take a look at what the client tools of SQL Server 2000 are-- enterprise manager, query analyzer, profiler, service manager, client-side network utilities, server network utilities, import and export data (DTS), and so on.

Server components and client tools are functionally compatible, and client tools need to express the richest functions of server components in the simplest form; server components and client tools are physically discrete. Say a big vernacular: they are not the same program! For client tools to connect with server components, you need some dynamic link libraries for communication. The communication libraries of SQL Server 2000 support a variety of network protocols, such as TCP/IP, named pipes, and so on.

At this point, the problem is very clear: as long as the client tools and server components and functions are matching (compatible), we can connect through a certain protocol, so as long as we install a set of client tools on our machines, we can connect to SQL Server servers around the world, of course, this requires the other party to open sufficient permissions.

Tip: installing SQL Server 2000 is actually installing server components and client tools. Of course, we can choose to install both server components and client tools, or just one of them, or even less.

III. The issue of version

There are many versions of SQL Server 2000: enterprise, Development, Standard, personal, and so on. Each version contains basically the same client tools, while the server components may be somewhat different. So before installing SQL Server, you must refer to the "operating system and SQL Server" version compatibility table (figure 1) to select the appropriate SQL Server version according to the operating system.

Figure 1

IV. On examples

Before you start installing SQL Server, there is another concept to explain, and that is the SQL Server instance. We mentioned earlier that the SQL Server server component is made up of four Windows service programs. In practice, we may install all or only some of the server components, but we all need a unified concept to mark a set of SQL Server services, which is the SQL Server instance.

Tip: it can be understood that to install the SQL Server server component is to create a new SQL Server instance (or, of course, to add or subtract the service component from the original instance). SQL Server 2000 allows you to create multiple instances in the same operating system, although we don't normally do so.

If ● installs only one instance of SQL Server, you do not need to specify the instance name when SQL Server is installed, and the default name is automatically used. Then the name of the computer in the SQL Server domain is the name of the SQL Server instance; when you connect to the SQL Server instance using the IP protocol, you can use the IP address to represent the SQL Server 2000 instance.

● if multiple instances of SQL Server 2000 are installed in an operating system, you need to specify the instance name at the time of SQL Server installation.

SQL Server 2000 instances can be marked in the form of "computer name instance name" in the SQL Server domain, and "IP address instance name" can be used to represent SQL Server 2000 instances when connecting to SQL Server instances using the SQL Server protocol.

Fifth, installation practice

The installer for SQL Server 2000 is very intelligent, and basically users just need to follow the prompts to select the default item. Below, the author selects some settings that need to be paid attention to to explain.

● selects "create a new SQL Server instance..." As shown in figure 2:

● chose to install Server and client tools, as shown in figure 3:

● sets the startup mode for the service, and there are two services, SQL Server and SQL Server agent. In fact, it is MSSqlServer and SQLServerAgent mentioned earlier. Here our operating system starts them with a "local system account", as shown in figure 4:

● selects "mixed mode" for authentication, as shown in figure 5:

VI. A glimpse of your face

After the installation, you must be eager to appreciate its elegant demeanor. Don't worry, let's first make sure that the database server has been started. We mentioned earlier that the core of SQL Server 2000 is made up of four server components, of which the one that provides database services is MSSqlServer, and now we just want to make sure that it has been started.

1. Service Manager

● selects the name of the native SQL Server instance in the "Server" column

● selects SQL Server in the "Services" column (that is, MSSqlServer above)

● presses the start / continue button to start the MSSqlServer service

● starts normally:

two。 Enterprise Manager

Open Enterprise Manager, expand the database project of the database native SQL Server instance node, and you can see that SQL Server has installed six databases automatically.

The ● master database records all system-level information for the SQL Server system.

The ● tempdb database holds all temporary tables and temporary stored procedures.

The ● model database is a template for users to create a database.

The ● msdb database is used by the SQL Server agent to schedule alerts and jobs and record various operations.

● northwind and pubs are sample databases, and we will often use them for demonstration in the future.

Except for northwind and pubs, the other four databases are maintained by SQL Server itself and generally do not require user intervention.

At this point, the study on the "installation method of SQL Server2000" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

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.