Comment déployer les bases de données App-V à l’aide de scripts SQL
Utilisez les instructions suivantes pour utiliser des scripts SQL, plutôt que Windows Installer, pour :
- Installer les bases de données App-V 5.1
- Mettre à niveau les bases de données App-V vers une version ultérieure
Remarque
Si vous avez déjà déployé la base de données App-V 5.0 SP3, les scripts SQL ne sont pas nécessaires pour effectuer la mise à niveau vers App-V 5.1.
Comment installer les bases de données App-V à l’aide de scripts SQL
Avant d’installer les scripts de base de données, passez en revue et conservez une copie des termes du contrat de licence App-V. En exécutant les scripts de base de données, vous acceptez les termes du contrat de licence. Si vous ne les acceptez pas, vous ne devez pas utiliser ce logiciel.
Copiez le
appv_server_setup.exe
à partir du média de mise en production App-V vers un emplacement temporaire.À partir d’une invite de commandes, exécutez
appv_server_setup.exe
et spécifiez un emplacement temporaire pour extraire les scripts de base de données.Exemple:
appv_server_setup.exe /layout c:\<temporary location path>
Accédez à l’emplacement temporaire que vous avez créé, ouvrez le dossier extrait
DatabaseScripts
et passez en revue le fichier Readme.txt approprié pour obtenir des instructions :Base de données de gestion :
ManagementDatabase
sous-dossierBase de données de création de rapports :
ReportingDatabase
sous-dossier
Attention
Le fichier readme.txt dans le ManagementDatabase
sous-dossier est obsolète. Les informations contenues dans les fichiers Lisez-moi mis à jour ci-dessous sont les plus actuelles et doivent remplacer les informations lisez-moi fournies dans les DatabaseScripts
dossiers.
Important
Le script InsertVersionInfo.sql n’est pas requis pour les versions de la base de données de gestion App-V ultérieures à App-V 5.0 SP3.
Mise à jour du contenu du fichier README de la base de données de gestion
******************************************************************
Before you install and use the Application Virtualization Database Scripts you must:
1.Review the Microsoft Application Virtualization Server 5.0 license terms.
2.Print and retain a copy of the license terms for your records.
By running the Microsoft Application Virtualization Database Scripts 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
Mise à jour du contenu du fichier README de la base de données de rapports
******************************************************************
Before you install and use the Application Virtualization Database Scripts you must:
1.Review the Microsoft Application Virtualization Server 5.0 license terms.
2.Print and retain a copy of the license terms for your records.
By running the Microsoft Application Virtualization Database Scripts 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
InsertVersionInfo.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
InsertVersionInfo.sql
Permissions.sql
## ScheduleReportingJob.sql