Capítulo
Ítem 10: El estudiante no comprende lo que es una letra, una palabra y una oración.
3.6.5 Entrevista a la psicóloga (Ver anexo 6)
This section describes how to install the initial version of SQL Server 2005 Enterprise/Standard/Workgroup Edition, which must be installed from the Microsoft SQL Server 2005 DVD.
The installation of SQL Server 2005 is interactive. In most of the dialog boxes you can accept the default settings, with the following exceptions:
l In theComponents to Installwindow, select the optionSQL Server
Database Servicesand clickAdvanced. TheComponents to Install window does not appear in the Workgroup Edition.
l In theFeature Selectionwindow, expandSQL Server Database Services. l UnderData Files, select the entryWill be installed on local hard drive
from the context menu.
l UnderShared (Management) Tools, select the entryWill be installed
on local hard drivefrom the context menu.
l In theFeature Selectionwindow, expandClient Components. l UnderManagement Tools, select the entryWill be installed on local
hard drivefrom the context menu. This installs the graphical program SQL Server Management Studio.
l UnderDocumentation,Samples, andSample Databasesyou can, if you
wish, selectWill be installed on local hard drivefrom the context menu. This installs the SQL Server 2005 online documentation.
l Note the following in theService Accountwindow:
o Do not use theNetworkServiceaccount.
o Click the optionUse a domain user accountand enter the user name, password and domain name. The domain user account does not require administrator authorization. You can use the domain user
account for all SQL services.
If you enter a local Windows user account here, use the account with the least privileges and the highest security level.
Microsoft recommends that user accounts that are used to log on as a service have thePassword never expiresoption activated and that they have strong passwords. Otherwise, follow the Microsoft
documentation “How to: Change the Password of the Accounts Used by SQL Server” if the SQL Server is running under an account for which the password is to be changed.
There are, however, a few exceptions for using a local Windows user account:
n If remote procedure calls, replication, backing up to network drives, heterogeneous joins that involve remote data sources, SQL Server Agent mail features and SQL Mail are to be used on the SQL Server for other applications, the local Windows account is not sufficient.
n In fail cluster installations, local system and local service accounts are not allowed.
The SQL Server 2005 Readme files and the SQL Server 2005 Books Online contain further details under the heading “Service account“. Alternatively, you can select the optionCustomize for each service accountand choose a separate service account for each service, e.g. an integrated system account:
n Assign theLocal Systemaccount for theSQL Server Serviceand SQL Server Agentservices, and theLocal Serviceaccount for the SQL Server Browserservice.
You can still change the service-account assignment after the installation using the SQL Server Configuration Manager. For detailed information on this, see the SQL Server 2005 online documentation, heading “Service account“.
The installation procedure for the Enterprise/Standard/Workgroup Editions is similar.
Installing service packs
After installation of the initial version of SQL Server 2005 the
Enterprise/Standard/Workgroup Editions must be updated with the latest service pack.
This section describes the currently latest Service Pack 4.
If your SQL Server system has Internet access, you can update via the Microsoft Update web page (http://www.update.microsoft.com). Click theCustombutton to list the available updates.
Otherwise, find a system with Internet access and download the service pack from the Microsoft Download Center SQL Server instance
(http://www.microsoft.com/downloads):
1. In the fieldSearch Download Center, enterSQL Server 2005and press Enteror click theSearchbutton. You can sort the downloads by release date.
2. Select the current service pack from the results list.
3. In theChange Languagelist, select the language of the installed SQL Server.
4. ClickDownloadto download the file.
5. In the window that opens, clickSaveand then select the storage location for the file.
On Windows Server 2008 mark in theAdditional Informationwindow the optionLaunch the User Provisioning Tool.
Before you perform the update installation, you must stop all applications and services which are connected to the server instance. SQL Server Management Studio and theAdd or Remove Programs window must be closed.
l Start the installation.
The installation is interactive and you can accept the default values. The updated components are shown in theFeature Selectionwindow. After the installation, the system is restarted.
For setting up high availability you can configure an automatic restart for the ServerView services and SQL Server services. For further information, see
"ServerView services" on page 167.
3.13
Configuring a remote SQL Server
To configure a remote SQL Server, proceed as follows: 1. Login as the local administrator.
2. The following services for the SQL Server instance must be started on the remote system:
SQL Server SQL ServerAgent SQL Server Browser
The servicesSQL ServerandSQL Server Agentshould run under a domain user account. For security reasons this account should not be a member of Windows groupAdministrators.
Microsoft recommends that user accounts that are used to log on as a service have thePassword never expiresoption activated and that they have strong passwords. Otherwise, follow the Microsoft documentation "How to: Change the Password of the Accounts Used by SQL Server" if the SQL Server is running under an account for which the password is to be changed.
This domain user account must belong to the same domain where the remote system is connected to.
If both systems are connected to the same domain, the services can also run under the service accountLocal System. This account has high privileges and is not recommendable for security reasons. TheSQL Server Browser service runs under service accountLocal Serviceby default.
Use a database administration tool to change the startup account for SQL Server. This ensures to automatically assign all the required permissions and Windows user rights to the new startup account for you.
Use SQL Server Configuration Manager: 1. Click onSQL Server <version> Services. 2. Stop the services for changing the account.
3. Change via the context menu entryPropertiesthe service account. 4. Start the services.
TheSQL Serveris restarted automatically.
3. Accesses to the remote SQL Server are authenticated via the Windows domain user accounts of the Operations Manager services.
If you want to do an "Operations Manager installation without SQL Server "sysadmin" access" skip the current step. Please refer to"Overview of Windows accounts and access rights" on page 101and then return to the next step 4.
Therefore, for the domain user account
l under which you will be logged on to the system during the Operations
Manager installation,
l in the Operations Manager installation windowRemote DB(for a new
installation) orServerView Service Logon Informationfor an upgrade installation
l in the Operations Manager installation windowUpdate Management
Logon Information,
you must bear in mind the following:
l The domain user accounts must belong to the same domain as the
server on which Operations Manager is installed.
l The domain user accounts must be created in SQL Server asLoginusing
the SQL Server administration tools.
l These logins must also be assigned a certain server role. This role
include the authorization necessary for installing and running the application.
To set up a user account, proceed as follows:
1. Log in as the administrator on the remote system.
2. Start the program SQL Server Management Studio for database administration.
3. Select the SQL Server instance or connect to it. 4. SelectSecurity–Logins.
5. SelectNew Loginfrom the context menu. TheLogin - Newwindow opens.
6. Enter the name for the domain user account underLogin nameor Name. You can keep the other settings.
7. Switch to theServer Rolestab.
8. SelectsysadminorSystem Administratorsas the server role. 9. ClickOK.
4. Remote access (via TCP/IP) to the corresponding SQL Server instance must be activated as follows.
1. Open the SQL Server Configuration Manager by selectingStart–All Programs–Microsoft SQL Server <version>–Configuration Tools– SQL Server Configuration Manager.
2. SelectSQL Server <version> Network Configuration.
3. ClickProtocols for <instance>. A list of protocols and their status is displayed.
4. Check the settingProtocol for <instance>.
5. The status for the TCP/IP protocol must beEnabled. 6. If not, activate TCP/IP for the instance.
5. For remote access to the SQL Server instance, a static port is required. Either use an unnamed SQL Server instance or configure a static port for a named instance.
To check the port configuration of a named instance, proceed as follows: 1. Open theRegistration Editor.
2. Search for the following entries:
l For an SQL Server 2014 instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL12.<Instance
l For an SQL Server 2012 instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.<Instance
Name>\MSSQLServer\SuperSocketNetLib\Tcp\IPAll
l For an SQL Server 2008 R2 instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.<Instance
Name>\MSSQLServer\SuperSocketNetLib\Tcp\IPAll
l For an SQL Server 2008 instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.<Instance
Name>\MSSQLServer\SuperSocketNetLib\Tcp\IPAll
l For an SQL Server 2005 instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.<n>\MSSQLServer\SuperSocketNetLib\Tcp\IPAll
In SQL Server 2005,MSSQL.<n>identifies the number of instance on the server with.<n>= .1..16 (e.g.MSSQL.1). As of SQL Server 2008, the internal version number (10, 10_50, 11) suffixed with the instance name is used:
MYSQL<internal version number>.<Instance Name>. 3. Check the values forTCPDynamicPortsandTCPPort. If the value for
TCPDynamicPortsis not set, SQL Server always uses a static port. You will see the port number underTCPPort.
If a static port was configured previously, the SQL Server instance must be restarted for the changes to the port configuration to take effect.
The static port for a named instance can be assigned via SQL Server Configuration Manager. The procedure is described in SQL Server Books Online "Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager)".
If necessary, allow via firewall administration program the following port for the SQL Server instance:
l Add for program SQL Server and protocol TCP either the default port
number 1433 or the port number given under TCPPort in the Registration Editor.
l Add for program SQL Server and protocol UDP port number 1434.
7. When installing SQL Server in another, but trusted domain, the SQL Server must be accessible via netbios name. You can do this by expanding the DNS Suffix Search List.
1. Log on to the SQL Server machine. 2. Look at the current DNS Suffix Search List.
Open a command prompt window and typeipconfig /all.
3. In theWindows IP Configurationentry you will find the DNS Suffix search list. The suffix of the domain to which the central management station is connected must be listed.
4. If not, you can change it e.g. by configuringAppend these DNS suffixes:
1. SelectControl Panel–Network and Sharing Center. 2. ClickPropertiesand clickInternet Protocol Version.
3. ClickPropertiesand clickAdvancedfor the DNS server address. 4. In theDNStab, select the optionAppend these DNS suffixes (in
order)and clickAdd.
5. Insert the TCP/IP Domain Suffix of the domain to which the central management station is connected to.
Further procedure on the management station
If you followed all instructions in "Operations Manager installation without SQL Server "sysadmin" access" skip the following steps 1 to 3 and go on with step 4.
1. Log on as local administrator.
2. Add the domain user account under which you want to perform the
Operations Manager installation and all further domain user accounts which you specify for services during the installation, as for example in the
Remote DBwindow,ServerView Service Logonwindow and in the Update Management Logon Informationwindow to theAdministrators group.
3. Log on under this domain user account.
4. Start ServerView Operations Manager installation and select in theSelect SQL Serverwindow theUse existing remote SQL Serveroption,"Menu- driven installation of Operations Manager software" on page 140.
5. On a new installation enter in theRemote DBwindow the corresponding values,"Remote DB window" on page 142. The local service ServerView Services will run under this account and will have access to the remote SQL Server via the SQL Server Login you created above.
6. In the otherLogon Informationwindows enter the same domain user account or a further domain user account for which you have created a SQL Server Login.
7. In the other windows fill in as described in section"Menu-driven installation of Operations Manager software" on page 140.
If you want to change the service account ofSQL ServerandSQL Server Agent after the ServerView Operations Manager installation you must additionally give on remote system write admission to the SQL Server backup folder
DbBackupPathfrom%windir%\ServerViewDB.inifile and to the files below. Upgrade installation
When you installed ServerView Operations Manager, you specified a user name and password for the ServerView services in theRemote DBwindow.
In an upgrade installation you must enter the password in theServerView Service Logon informationdialog again because it is not saved.