Validación de la propuesta

This upgrade method is also called an “in-place“ upgrade and is offered as an installation option by the SQL Server setup. The upgrade is performed when you execute the SQL Server setup and select the appropriate option offered there. During the SQL Server upgrade, all databases installed in this instance - i.e. also the ServerView database - are automatically upgraded.

Operations Manager remains installed on the system. Only while the upgrade is being performed must accesses to Operations Manager be temporarily stopped.

An in-place upgrade requires the following:

l An installed instance of SQL Server in a particular edition can only be

upgraded to a corresponding compatible edition of SQL Server. An SQL Server 2005 Express instance can, for example, be upgraded to an SQL Server 2008 Express instance, but not directly to an SQL Server 2008 Standard or Enterprise Edition.

l You cannot perform an in-place upgrade from an installed 32-bit edition of

SQL Server to a 64-bit edition of SQL Server.

l Language dependencies must also be taken into account:

During an in-place upgrade it is not possible to upgrade a localized version of SQL Server (for example, the German version) to a different-language version of SQL Server. For an in-place upgrade, therefore, you must install the new SQL Server instance in the same language version as the old instance. Only an English version of SQL Server can be upgraded to a localized version in a different language.

The installation requirements are also checked by the SQL Server setup process itself, with messages or warnings being output if necessary.

If the existing SQL Server instance was installed by Operations Manager, the installation language is English or Japanese.

You can also check the product version, installation language and edition of the installed SQL Server instance beforehand as follows:

1. Find out the contents of theServer_Instanceparameter in the

configuration fileServerViewDB.ini. The configuration file is located in the <windir>directory.

2. Open the input prompt. 3. Enter the following commands:

osql -S <server_instance> -E xp_msver

GO

select @@version GO

You will find the necessary information on the version and language in the command output under2 ProductVersionand3 Language.@@version

gives you the edition.

You quit osql with thequitcommand. Preparing for installation

l While the SQL Server instance is being upgraded, the setup checks the

necessary hardware and software requirements. You can find out these requirements in advance from the web pages of the Microsoft Download Center for the SQL Server version required or from the SQL Server online documentation available on the Internet.

l To install an SQL Server Express Edition, you may have to download the

required software from the Microsoft Download Center and install it yourself in advance. All other editions of SQL Server come with the necessary software components and install them when you start the setup.

l You should also find out from the relevant SQL Server online documentation

which version and edition upgrades from SQL Server to later SQL Server editions Microsoft supports in the setup.

l Find out the type (default instance or named instance) and name of the

installed SQL Server instance. You have to specify the instance name and type while executing the SQL Server installation, so that the SQL Server setup upgrades the correct SQL Server instance. You will find this information in the configuration fileServerViewDB.ini(in the<windir>directory) in the Server_InstanceandInstanceparameters:

o If there is noInstanceparameter, the instance is a default one. Under Server_Instance, only the server name (usually(local)) is given. o For a named instance, the instance name is given underInstance. The

Server_Instanceparameter contains the information <server_name>\ <instance_name>.

Necessary actions before the upgrade

l Back up the databases of the relevant instance.

l Close all applications which have access to the relevant SQL Server instance. l Stop all dependent services, in particularServerView Servicesand

l Install the required software for the installation of the new SQL Server

version and edition. Performing the upgrade

You upgrade the instance by executing the SQL Server setup. The installation can be performed interactively for all editions of SQL Server. It is recommended that you always use the latest service pack. If possible you should also perform a Microsoft update after the setup, so that you receive any current security updates for the upgraded SQL Server version from Microsoft.

Upgrading from older SQL Server editions

Bear in mind the following during the upgrade to a newer SQL Server version:

l During the procedure, the SQL Server setup program detects all installed SQL

Server instances on the server and displays them for selection and configuration in various interactive steps.

l First of all, in theSelect Instancewindow you must select the instance

name from the displayed list. If there are several instances installed, the setup preselects a standard instance of SQL Server, if there is one. An SQL Server Express instance used by ServerView is normally installed as a named instance (instance nameSQLSERVERVIEW). You can find out the name and type of the instance used by ServerView from the configuration file

ServerViewDB.ini(in the<windir>directory) as described above.

l In the laterInstance Configurationwindow, you must then check the

instance name again and specify whether you want to install a standard instance or a named instance.

l For the remaining configuration options, apart from the instance name, you

can accept the default options.

Upgrading from an older SQL Server Express version

The Microsoft documentation contains a detailed upgrade support matrix for any version and edition of SQL Server. Please check the supported path for your version of SQL Server Express in advance.

For example, additional tools allow you to perform the following upgrades:

l An installed SQL Server 2005 Express, you can upgrade to SQL Server 2008

Express with Tools).

If you want to install the extended editions, however, you must execute the installation program again after the upgrade in order to add the additional components.

l An installed SQL Server 2005 Express, you can upgrade to SQL Server 2012

Express or SQL Server 2014 Express or its extended versions with additional tools (SQL Server 2012/2014 Express with Tools).

l An installed SQL Server 2008 Express, you can upgrade to SQL Server 2012

Express or SQL Server 2014 Express or its extended versions with additional tools (SQL Server 2012/2014 Express with Tools).

You can get the editions of SQL Server 2008/2012/2014 Express you require from the Microsoft Download Center. After starting the setup, select the option Upgrade from SQL Server 2005 / Upgrade from SQL Server 2008 / Upgrade from SQL Server 2008 R2 / Upgrade from SQL Server 2012. During the installation you must then specify in a later follow-up dialog the SQL Server instance to be upgraded.

Upgrading from all other SQL Server editions

All SQL Server editions can usually be upgraded to a corresponding edition of a higher SQL Server version, provided the upgrade path is supported by Microsoft version and edition restrictions. Please check the supported upgrade path for your version and edition in the Microsoft documentation in advance. Full editions of SQL Server are not available free of charge from the Download Center but must be licensed and installed from your SQL Server installation medium. Necessary actions after the upgrade

After the in-place upgrade of the instance, you must perform the following steps for all versions of SQL Server:

1. Check whether theSQL Server (<instance_name>)service was started. 2. For editions other than SQL Server Express:

Check whether theSQL Server Agent (<instance_name>)service was started.

If you are using a remote SQL Server for Operations Manager, you must perform the additional steps on the management station. To do this, log on to the management station under the user account specified in the%windir%\ServerViewDB.inifile under the entriesDomainandUsername.

3. For SQL Server Express:

Check whether the Windows serviceTask Schedulerhas started. 4. Internal backup jobs of Operations Manager must now be set up again

before you can restart Operations Manager.

The following prerequisites must be met to ensure correct functioning of the upgrade tool provided by the ServerView Operations Manager installation:

l SQL Server Client tools must be installed and accessible via the

PATHenvironment variable in their default location on the CMS:

<Program Files>\Microsoft SQL

Server\<version>\Tools\Binn\(with <version> in 90\100\110).

l The calling account must be a member of thesysadminserver

role in SQL Server.

l The Windows command prompt used to call the tool must be

opened with full administrator rights. Proceed as follows:

1. Open the input prompt. 2. Switch to the directory:

<installation_path>\ServerView Services \scripts\ServerView\Tools 3. Execute the following batch file, which you will find in this directory

after upgrading to an SQL Server 2008, SQL Server 2012 edition, or SQL Server 2014 edition:

l SVCreateJobs_Upgrade2008 l SVCreateJobs_Upgrade2012 l SVCreateJobs_Upgrade2014

4. During the execution, answerRenamed SQL Server Instance [Y/N] ?withN.

5. All necessary upgrade steps for Operations Manager will be executed from this batch file. The individual steps will also be logged in the log file <DbApplicationFolder>\SVCreateJobs_Upgrade2008.logor

<DbApplicationFolder>\SVCreateJobs_Upgrade2012.log(for SQL Server 2012/2014). You can find out the contents of theDbApplicationFolder parameter from the configuration fileServerViewDB.ini(in the<windir> directory).

6. After successful execution, start the servicesServerView Servicesand ServerView Download Service.

7. Then check whether the backup jobs for the ServerView database have been set up and can be executed.

For SQL Server Express editions the jobs were set up via the Windows Task Scheduler and therefore can only be monitored via this tool:

l To do this, openControl Panel–Scheduled Tasksand you will see a

list of jobs and their schedules.

For all other editions of SQL Server, the serviceSQL Server Agentis used to set up the jobs. In this case, check the jobs and schedules via SQL Server Management Studio.

l Start SQL Server Management Studio.

l Click the SQL Server instance and select the entrySQL Server Agent. l UnderJobsyou will see the jobs that have been set up. You can view

the current schedule for each job withView History. 3.15.1.2 Moving the ServerView database

If you do not want to or cannot perform an in-place upgrade of the entire SQL Server instance, you can instead move the ServerView database from an installed SQL Server instance into a new SQL Server instance, thus migrating it. This procedure is also referred to in the Microsoft online documentation for SQL Server as a "side-by-side" upgrade. You must choose this variant if an in-place upgrade for your SQL Server edition is not supported by Microsoft. This is the case, for example, if you want to upgrade from a 32-bit SQL Server edition to a 64-bit SQL Server edition.

In the Microsoft online documentation for the SQL Server version required, you can find out which version and edition upgrades from SQL Server/SQL

ServerExpress to later SQL Server editions are supported by Microsoft. With this upgrade method, a new SQL Server instance is installed side-by-side with the existing one. The ServerView database is first detached from the installed instance and then attached to the new instance. Operations Manager also remains installed on your system with this method.

You must install the new SQL Server instance on the same system as the old one, so that the client configuration for Operations Manager is retained. So that, the old and new instances of SQL Server cannot be installed side-by-side under the same instance name.

You must either

l Uninstall the SQL Server instance after the database is detached

and before the new instance is installed, or

l Install the new SQL Server instance under a different instance

name. Note the following:

Switching the instance type is not supported for the upgrade of the ServerView database. For the upgrade you can install a named instance under a different name, but not switch from a named instance to a default instance (or vice versa).

Preparing for installation

l During the installation of the newer instance, the necessary hardware and

software requirements are checked. For information on this, see, for example, the product pages for the new SQL Server version in the Microsoft Download Center.

l To install an SQL Server Express Edition, you may have to download the

required software from the Microsoft Download Center and install it yourself in advance. All other editions of SQL Server come with the necessary software components.

l Find out the type (default instance or named instance) and name of the

configuration fileServerViewDB.ini(in the<windir>directory) in the Server_InstanceandInstanceparameters:

o If there is noInstanceparameter, the instance is a default one. Under Server_Instance, only the server name (usually(local)) is given. o For a named instance, the instance name is given underInstance. The

Server_Instanceparameter contains the information<server_name>\ <instance_name>.

l Find out the current path names of the ServerView database files. The path

names are needed for attaching the database to the newer SQL Server instance.

You can find out the path names as follows using the SQL Server Management Studio:

1. Start the tool and connect to the installed SQL Server instance. 2. Select the databaseServerViewDB.

3. SelectPropertiesfrom the context menu. After selecting files, you will find the path name.

You can find out the path names using osql (or sqlcmd) as follows: 1. Open the input prompt and enter the following commands:

osql -S <Server_Instance> -E EXEC sp_helpfile

GO

Thefilenamecolumn contains the path details.You quit osql with thequit command.

Necessary actions before the upgrade

l In the existing SQL Server instance, back up theServerViewDBdatabase so

that you have an up-to-date backup.

l Close all applications which have access to the relevant SQL Server instance. l Stop all dependent services, in particularServerView Servicesand

ServerView Download Service.

l Install the required software for the installation of the new SQL Server

Performing the upgrade

l Detach the ServerView database from the existing SQL Server instance.

You can either do this with SQL Server Management Studio, or directly by calling an SQL Server procedure from an input prompt with osql.

If you want to use a management tool, you can find out from the online help for the tool you are using how to detach the database.

If you are using an input prompt, proceed as follows:

1. Open the input prompt and enter the following commands:

osql -S <server_instance> -E

EXEC sp_detach_db @dbname='ServerViewDB' GO

You quit osql with thequitcommand.

l Detach does not delete the database files from SQL Server; instead they

remain in the relevant storage location. You can either leave the files there or copy them to a different directory. In any case you must specify the current path name in the new instance when you attach the database later.

l If the name of the SQL Server instance is not to be changed, you must now

uninstall the existing SQL Server instance.

l Install the new SQL Server instance:

o For an SQL Server Express Edition, start the installation from the files downloaded from the Download Center.

o For all other editions of SQL Server you can start the installation directly from your installation medium (DVD or iso image).

l If the instance name is not to be changed and a previous SQL Server

instance was uninstalled, then perform the installation with the same type (default instance or named instance) and name (for a named instance), e.g.SQLSERVERVIEWfor SQL Server Express edition.

l Note the following when installing SQL Server Express:

Deactivate the optionHide advanced configuration optionsin the Registration Informationwindow, otherwise you will not be able to assign an instance name other than the default nameSQLEXPRESSduring the installation.

l Then attach the database as follows:

1. Open SQL Server Management Studio and connect to the new instance. 2. SelectNew Queryand enter the following command in theQuery

window, where<data_path>is the path name of the ServerView database files on your system.

CREATE DATABASE ServerViewDB

ON PRIMARY (FILENAME='<data_path>\ServerViewDB.mdf') LOG ON (FILENAME='<data_path>\ServerViewDB_log.LDF') FOR ATTACH

l Following the attachment, execute the following command to check the

consistency and to update:

DBCC UPDATEUSAGE('ServerViewDB')

l If you are using the SQL server as a remote SQL server for Operations

Manager, set up the user account as described in section"Configuring a remote SQL Server" on page 92. On the management station you will find the user account in the%windir%\ServerViewDB.inifile underDomain andUsername.

l Set up the user account under which theServerView Servicesand

ServerView Download Serviceare registered in SQL Server as of 2008 as an authorized SQL administrator, see"Adding a user account with SQL Server administrator rights" on page 83.

l If you are using SQL Server as of 2012 as a local SQL Server, also add the

LOCAL SYSTEMaccount as an authorized administrator. Necessary actions after the upgrade

After the side-by-side upgrade of the instance, you must perform the following steps for all versions of SQL Server:

If you are using the SQL server as a remote SQL server for Operations Manager, you must perform the additional actions on the

management station, logging on as the user who is entered on there in the%windir%\ServerViewDB.inifile underDomainandUsername. 1. For an Express Edition, check whether the serviceWindows Task Scheduler

is started before you continue with the upgrade.

Agent <instance_name>is started.

3. Internal backup jobs of Operations Manager must now be set up again before you can restart Operations Manager.

The following prerequisites must be met to ensure correct functioning of the upgrade tool provided by the ServerView Operations Manager installation:

l SQL Server Client tools must be installed and accessible via the

PATHenvironment variable in their default location on the CMS:

<Program Files>\Microsoft SQL

Server\<version>\Tools\Binn\with <version> in 90\100\110.

l The calling account must be a member of thesysadminserver

In document La atención a los indicadores de dislexia y su incidencia en el desarrollo de las habilidades de la lecto escritura de los niños de 7mo grado de escuela fiscal de educación básica Mayor Ignacio Viteri Mosquera (página 142-161)