Nota:
El acceso a esta página requiere autorización. Puede intentar iniciar sesión o cambiar directorios.
El acceso a esta página requiere autorización. Puede intentar cambiar los directorios.
Se aplica a: Windows Server 2016
Use las siguientes instrucciones para usar scripts SQL, en lugar de Windows Installer, para:
- Instalar las bases de datos de App-V
- Actualizar las bases de datos de App-V a una versión posterior
Nota
Si ya has implementado una base de datos de App-V 5.0 SP3 o posterior, los scripts SQL no son necesarios para actualizar a App-V para Windows.
Cómo instalar las bases de datos de App-V mediante scripts SQL
Antes de instalar los scripts de la base de datos, revise y guarde una copia de los términos de licencia de App-V. Al ejecutar los scripts de la base de datos, acepta los términos de licencia. Si no los acepta, no debe utilizar este software.
Copia appv_server_setup.exe desde los medios de versión de App-V a una ubicación temporal.
Desde un símbolo del sistema, ejecute appv_server_setup.exe y especifique una ubicación temporal para extraer los scripts de la base de datos.
appv\_server\_setup.exe /layout c:\\_<temporary location path>_Vaya a la ubicación temporal que ha creado, abra la carpeta DatabaseScripts extraída y revise el archivo dereadme.txt adecuado para obtener instrucciones:
Base de datos Ubicación del archivo readme.txt que se va a utilizar Base de datos de administración Subcarpeta ManagementDatabase Base de datos de informes Subcarpeta ReportingDatabase
Precaución
El archivo readme.txt de la subcarpeta ManagementDatabase está obsoleto. La información de los archivos Léame actualizados que figuran a continuación es la más reciente y debe reemplazar la información Léame proporcionada en las carpetas DatabaseScripts .
Importante
El script de InsertVersionInfo.sql no es necesario para las versiones de la base de datos de administración de App-V posteriores a App-V 5.0 SP3.
Se actualizó el contenido del archivo LÉAME de la base de datos de administración
***********************************************************************************************************
Before you install and use the Application Virtualization Database Scripts, you must:
- Review the license terms.
- Print and retain a copy of the license terms for your records.
By running the App-V you agree to such license terms. If you do not accept them, do not use the software.
***********************************************************************************************************
Steps to install "AppVManagement" schema in SQL SERVER.
## PREREQUISITES:
1. Review the installation package. The following files MUST exist:
SQL files
---------
Database.sql
CreateTables.sql
CreateStoredProcs.sql
UpdateTables.sql
Permissions.sql
2. Ensure the target SQL Server instance and SQL Server Agent service are running.
3. If you are not running the scripts directly on the server, ensure the
necessary SQL Server client software is installed and available from
the specified location. Specifically, the "osql" command must be supported for these scripts to run.
## PREPARATION:
1. Review the database.sql file and modify as necessary. Although the
defaults are likely sufficient, it is suggested that the following
settings be reviewed:
DATABASE - ensure name is satisfactory - default is "AppVManagement".
2. Review the Permissions.sql file and provide all the necessary account information
for setting up read and write access on the database. Note: Default settings in the file will not work.
## INSTALLATION:
1. Run the database.sql against the "master" database. Your user
credential must have the ability to create databases.
This script will create the database.
2. Run the following scripts against the "AppVManagement" database using the
same account as above in order.
CreateTables.sql
CreateStoredProcs.sql
UpdateTables.sql
Permissions.sql
Contenido actualizado del archivo LÉAME de la base de datos de informes
***********************************************************************************************************
Before you install and use the Application Virtualization Database Scripts, you must:
- Review the license terms.
- Print and retain a copy of the license terms for your records.
By running the App-V you agree to such license terms. If you do not accept them, do not use the software.
***********************************************************************************************************
Steps to install "AppVReporting" schema in SQL SERVER.
## PREREQUISITES:
1. Review the installation package. The following files MUST exist:
SQL files
---------
Database.sql
UpgradeDatabase.sql
CreateTables.sql
CreateReportingStoredProcs.sql
CreateStoredProcs.sql
CreateViews.sql
Permissions.sql
ScheduleReportingJob.sql
2. Ensure the target SQL Server instance and SQL Server Agent service are running.
3. If you are not running the scripts directly on the server, ensure the
necessary SQL Server client software is installed and executable from
the location you have chosen. Specifically, the "osql" command must be supported for these scripts to run.
## PREPARATION:
1. Review the database.sql file and modify as necessary. Although the
defaults are likely sufficient, it is suggested that the following
settings be reviewed:
DATABASE - ensure name is satisfactory - default is "AppVReporting".
2. Review the Permissions.sql file and provide all the necessary account information
for setting up read and write access on the database. Note: Default settings
in the file will not work.
3. Review the ScheduleReportingJob.sql file and make sure that the stored proc schedule
time is acceptable. The default stored proc schedule time is at 12.01 AM (line 84).
If this time is not suitable, you can change this to a more suitable time. The time is in the format HHMMSS.
## INSTALLATION:
1. Run the database.sql against the "master" database. Your user
credential must have the ability to create databases.
This script will create the database.
2. If upgrading the database, run UpgradeDatabase.sql This will upgrade database schema.
2. Run the following scripts against the "AppVReporting" database using the
same account as above in order.
CreateTables.sql
CreateReportingStoredProcs.sql
CreateStoredProcs.sql
CreateViews.sql
Permissions.sql
ScheduleReportingJob.sql