Jaa

Install Service Manager on virtual machines

  • Artikkeli

This article provides guidance that you should consider when you install System Center - Service Manager in a Hyper-V virtual environment. If you're installing Microsoft SQL Server into an environment without Hyper-V, consult your vendor's documentation for guidance regarding the use of SQL Server.

Deploy SQL Server in a virtual environment

Before you deploy SQL Server in a Hyper-V environment, see Running SQL Server 2008 in a Hyper-V Environment. Keep the following in mind when you prepare a virtual environment for SQL Server:

  • Using a dynamic virtual hard drive (VHD) can decrease performance. We don't recommend using a VHD.

  • Allocate at least two virtual CPUs for the instance of SQL Server.

  • Don't allocate more virtual CPUs than the number of available logical CPUs.

  • If you observe a drop in Service Manager performance in a virtual environment, check CPU and memory utilization on the virtual machines that are hosting the instance of SQL Server and the Service Manager management server. If CPU utilization is near 100 percent, either allocate additional virtual CPUs or reduce the number of concurrent Service Manager console sessions.

Verify memory requirements

The amount of memory you've in your logical computer and the amount of memory you allocate to each virtual machine are critical. If you deploy an instance of SQL Server, Service Manager management server, and Service Manager console to the same virtual machine, the memory requirements are cumulative. You need enough memory to meet the requirements of each part of Service Manager. In this environment, 8 gigabytes (GB) of memory is the minimum recommended amount.

Deploy the databases in a virtual environment

If you're installing Service Manager and data warehouse databases on virtual machines, we recommend that you use one virtual machine for the Service Manager database and another virtual machine for the data warehouse databases. Furthermore, each virtual machine should be configured for two CPUs.

Next steps