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

Today, I will talk to you about how to install SQL Server effectively. Many people may not know much about it. In order to make you understand better, the editor has summarized the following contents for you. I hope you can get something according to this article.

Microsoft always tries to make its software installation as simple and smooth as possible, and the installation of SQL Server 2000 is no exception. After you start setupsql.exe from the x86 etup folder of the installation CD and fill in some details in the installation dialog box, the installation will continue without user intervention in a few minutes. You can even successfully install SQL Server 2000 without knowing what those options mean-just click "next" in most installation dialogs. However, I strongly advise you not to treat installation so rashly; pay attention to every option and make sure you fully understand the impact of each choice you make. Some poor decisions, such as incorrect collation settings, may be difficult to fix; others, such as accepting the default authentication mode, may create security.

Let's look at some key points about standard installation, including instance configuration, security, collation, and network libraries. Then let's explore the advanced options for unattended and remote installation.

Example

When you start the installation, perform a standard installation frequently (compared to remote or unattended installations). You call the setupsql.exe program to start the installation wizard. After the first two dialogs-Welcome and Machine name-you need to choose your instance configuration. SQL Server 2000 supports the installation of multiple instances of SQL Server on one machine. The installer displays two dialogs to give you the option to install the instance.

First, the installation selection dialog box shows you the choice of whether to install a new instance or upgrade an existing installation. If you choose to install a new instance, you will see the instance name dialog box displayed. You can specify an instance name or choose to install a default instance by default-if the default instance is not already installed on the machine.

There are a few things you need to consider when making a choice about installing an instance. If there is no default instance on the machine and you plan to use SQL Server 2000 and 7.0on the same machine, make sure you do not install SQL Server 2000 as the default instance. SQL Server 7.0does not support naming instances, so it must be the default instance. Except for uninstalling and reinstalling SQL Server, you cannot change the named instance to the default instance or vice versa. You also cannot change the instance name after the instance is installed. However, you can install SQL Server 7.0 after installing SQL Server 2000-if you haven't already installed a default instance.

If an installation of SQL Server 7.0 already exists, you can upgrade it-by selecting the upgrade path in the installation selection dialog box and indicating in the latter dialog that you want to upgrade the default instance. However, SQL Server 2000 will be the default instance, and SQL Server 7.0 will no longer exist on this machine. To keep both versions, install SQL Server 2000 as a named instance.

After installing SQL Server 2000, you can use backup and restore, detach and connect, data conversion services, or replication wizards to transfer SQL Server 7.0 databases to SQL Server 2000. Note that when you upgrade a previous version to SQL Server 2000, no matter which way you choose, you cannot specify more than one installation of the same copy of the database, so each installation must maintain its own copy of each database.

Another consideration involves a feature known as "version switching" in SQL Server 7.0, which allows SQL Server 7.0 and SQL Server 6.5 to coexist on the same machine. However, at the same time, only one installation can be active and the other is static. When you call version control, it activates the static installation and stops the active one. If the machine includes an installation of SQL Server 6.5. which does not coexist with SQL Server 7.0in the form of version control, the installer requires you to choose one of two options: upgrade SQL Server 6.5to the default instance of SQL Server 2000 and maintain a version control between the two versions; upgrade to a named instance of SQL Server 2000. Unlike upgrading from SQL Server 7.0-it overrides the current installation, the 6.5 installation remains on your computer-no matter which path you choose to upgrade to 2000.

If both 7.0,6.5 are installed and co-exist on the same machine in the form of "version control", and you do not want to upgrade an existing installation, you can safely install a named instance of 2000 on the same machine and use all three versions on the same machine. However, while coexisting in the form of version control, only one version can be run, and all named instances can run at the same time.

After explaining your instance options, we come to the installation type dialog box.

Custom installation

In the installation types dialog box, the installation wizard asks you to choose among three installation types: typical, minimum, and custom. If you choose typical or minimum, SQL Server uses default options for components and subcomponents, collations, and network libraries. Because a typical installation can potentially cause thorny problems, I strongly recommend that you always choose customization-even if you think it meets your installation needs by default. Some of the previously mentioned options-- especially collations-- are very difficult to change if you find that they do not meet the requirements after installation. Custom installation allows you to check those options again.

Safety

During the installation process, you specify security-related information in two dialogs: service account and authentication mode. In the service account dialog box, you enter the service account details of SQL Server and SQL Server Agent services. Each service is called in by the operating system using the account described in the dialog box and runs in the security context of this account in the operating system. For example, when you back up to a disk device, SQL Server checks to see if the login you use to log in to SQL Server has the appropriate "backup database" permissions. However, to create a backup file device and write, SQL Server must create a file on disk or network share, using the security context of the SQL Server service account.

Similarly, the SQL Server Agent service runs on the SQL Server, operating system, or network under the security context of the SQL Server Agent service account. Although an account that does not have administrative privileges locally can start the SQL Server service, it is a good idea to add the SQL Server service account to the local administrators group. Otherwise, you need to grant all the necessary permissions to the account in addition to the appropriate network permissions for the account.

If you try to start SQL Server Agent through a service account that doesn't have administrator privileges on the machine, it won't even start. And if SQL Server Agent performs operations on other machines on the network, such as replication or multi-server work, you should use a domain account with appropriate permissions on other machines. For example, in a single-domain, multi-server environment with three SQL Server machines, a master server controls automatic activity on the target server. Because the two parties (the primary server and the target server) need to communicate with each other, you need to ensure that the SQL Server Agent service account on the primary server has appropriate permissions on the target server, and vice versa. The easiest way to configure such an environment is to create a domain account, make it a member of the local administrators group on all servers, and use that account to invoke all SQL Server Agent services.

In the authentication mode dialog box, you can choose whether to allow only Windows authentication login (Windows authentication mode) or both Windows and SQL Server login (mixed mode). You can also specify a password for the SQL Server login of sa (System Administrator). Windows authentication mode is the default and most commonly used recommended security mode. However, for security reasons, I recommend that you choose mixed mode and provide a password for your sa account, and then change the authentication mode to Windows authentication mode after the installation and processing of some other security projects. If you choose Windows authentication mode as the security mode for your server, the installation process creates the sa login as invalid and without a password (because SQL Server authentication mode is invalid). You can change your sa password after installation-I strongly recommend it-but it is dangerous to choose Windows authentication mode in the first place because you may forget to change your password or use an empty password and think that sa is invalid.

No matter which mode you choose, the installer creates a Windows authenticated login for the BUILTINAdministrators group, which maps to the local machine's administrators group. The creation of this login means that all members of the local administrators group, including domain group domain administrators, are members of your SQL Server's system administrator (sysadmin) role. It's not always a good idea to give network and local administrators unlimited access to SQL Server, because it introduces security risks, so you may decide to remove BUILTINAdministrators from SQL Server's sysadmin role, or you may completely remove these automatically created logins from SQL Server and create a login for DBA members with sysadmin identity-- not a network administrator.

If you decide to follow these recommendations, this is enough: first, create a login as sysadmin for the DBA membership group, and then delete the BUILTINAdministrators login. If your server is in Windows authentication mode and you delete all sysadmin qualified logins before creating a login for DBA, you will find yourself locked out of SQL Server and unable to perform administrative tasks such as creating a new login. If you fall into this trap, you can still change the SQLServer authentication mode to mixed mode by changing the key value of the registry HKEY_LOCAL_MACHINE OFTWAREMicrosoftMicrosoft SQLServer instance name\ MSSQLServerLoginMode to 2, and then restart the SQLServer service after modification.

Although it is convenient to control the login mode of SQL Server through the registry, it also has a drawback. Anyone who has permission to edit registry key values, including network and local administrators, can change the authentication mode of SQL Server. If you use Windows authentication mode to install SQL Server,sa, it is invalid but still has a blank password. If you then change the SQL Server authentication mode to mixed mode (which makes the sa login valid), anyone can log in as sa. So make sure you change your sa password as soon as you finish the installation or choose mixed mode and provide a password for sa during the installation process.

Sorting rules

Next, you need to select the collation settings. Collation (Collation) settings in SQL Server 2000 are used to manage language-related behavior, uniqueness of object names and column values, and collation (sorting rules). In the collation Settings dialog box, you specify the collation and choose between the SQL Server collation and the Windows collation. If you need backward compatibility with previous SQL Server versions, choose the SQL Server collation-for example, if you plan to use replication between an earlier version of SQL Server and SQL Server 2000. Otherwise, select the Windows collation. The collation settings of SQL Server 2000, whether Windows or SQL Server, incorporate three separate settings in previous versions: character set, sort order, and Unicode collation. In addition to integrating the old three settings together

After reading the above, do you have any further understanding of how to effectively install SQL Server? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

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.