VMware: VirtualCenter 2.0.x and SQL 2005


 

Na een verse installatie van Windows 2003 SP2, SQL 2005 SP2 en VC 202 patch1 krijg ik de onderstaande foutmelding zodra ik de VC service wil starten.

vc2service_error

Dit kun je oplossen door de volgende stappen uit te voeren:

If the VirtualCenter Server service installs but does not start and logs the following error, this is a symptom that the SQL Server 2005 SP1 database is not configured correctly:

Failed to init tableDef: Column VER_ID does not exist in table VPX_VERSION. Database version may be incompatible.

This condition can occur if VirtualCenter Server was installed using a database login mapped to a user other than dbo. When the VirtualCenter login is the owner of the database, the login automatically maps to the dbo user.
There are two ways to achieve the correct configuration:

  • Configure a fresh installation.
  • Repair a fresh installation that does not start.

To configure a fresh installation:

  1. Connect to your SQL Server 2005 server with SQL Server Management Studio.
  2. Create a database login (*vclogin*) for VirtualCenter Server to use.
  3. Create a new database (*VCDB*) and change the owner from <default> to vclogin.
  4. Observe that vclogin maps to the dbo database user for VCDB.
  5. Change the default database for vclogin from master to VCDB.
  6. Install VirtualCenter Server according to the product documentation.

To repair a fresh installation that does not start:
If the database has already been created and VirtualCenter Server has already been installed, it is possible to modify the owner of the database with a system stored procedure. In the steps below, substitute <vcuser> and <vclogin> with your appropriate account names.

  1. Connect to your SQL Server 2005 server with SQL Server Management Studio.
  2. Go to the db_owner schema properties and change the owner from <vcuser> to dbo.
  3. Delete the <vcuser> database user (not the <vclogin> database login that maps to it).
  4. Open a new query window for the VirtualCenter database.
  5. Execute this command:
    EXEC sp_changedbowner @loginame = ‘<vclogin>’, @map = ‘true’
  6. Start the VirtualCenter Server service.

Reference the VirtualCenter Server Release Notes at http://www.vmware.com/support/pubs/vi_pubs.html for details on supported databases and client driver versions. For information how to identify your SQL Server version and edition, reference the Microsoft Knowlege Base article 321185 at http://support.microsoft.com/kb/321185.

De bovenstaande tekst komt van het volgende document: http://kb.vmware.com

Bij mij was dit niet de oplossing. Ik heb er uiteindelijk voor gekozen om geen gebruik te maken van een SQL account maar van een Windows (AD) account welke rechten had op VC database. Daarna starte de VirtualCenter Service gewoon op.

VMware: VirtualCenter Database Calculator


Bouke poste op het forum van http://www.vmug.nl/ de volgende url: http://www.vmware.com/support/vi3/doc/vc_db_calculator.xls

Deze Excel sheet stelt je in staat om de benodigde schijfruimte voor de VirtualCenter database te berekenen. Vooral in grootte omgevingen is dit een handige tool voor het plannen van de omgeving.

VMware: Virtualize SQL Server?


Op deze vraag heeft VMware een antwoord namelijk de volgende whitepaper: SQLServerWorkloads.pdf.

De bovenstaande whitepaper is een performance study van VMware en HP over hoe je een  SQL server wel of niet moet Virtualiseren.

Dit is de conclusie van de performance study:

The performance results we describe in this paper support the conclusion that running Microsoft SQL Server 2005 inside VMware virtual machines can provide an effective production-ready platform for running transaction-processing workloads.
Your IT organization can leverage the sizing data we present in this white paper to deploy Microsoft SQL Server successfully using VMware Infrastructure 3. By comparing effective workload throughput and resource utilization for your datacenter with the results presented in this paper, you can design and size your virtualized environment to meet your SLA targets.
The number of actual users and transactions you can support in a production environment will, of course, depend on the specific applications used and the intensity of user activity. The results of
Conclusions 12 VMware SQL Server Performance in a VMware Infrastructure 3 Environment
our tests clearly demonstrate that in a VMware Infrastructure 3 environment, the transaction throughput scales almost linearly even as the number of clients increases, for every configuration we tested. Our results show that the throughput rate of UP virtual machine is comparable for 32-bit and 64-bit environments. However, for SMP virtual machines, the throughput rate is slightly higher in a 64-bit environment compared to a 32-bit environment. Further, SMP virtual machines can service a higher number of users. One disadvantage of SMP virtual machines is that they have higher CPU costs per transaction than UP virtual machines. From a performance perspective, we recommend using SMP virtual machines rather than UP virtual machines for Microsoft SQL Server, and if possible, a 64-bit environment if your application stack supports it.

How To: Setup and Configure SQL 2005 (Express)


Het volgende artikel http://technet.microsoft.com/ legt uit hoe je de setup door moet lopen. Dit spreekt echter voor zich.

Het KB artikel KB914277 legt uit hoe je remote connections in kunt schakelen.

Om even verder op KB914277 in te gaan, laat ik even een aantal printscreens zien. Tevens laat ik gelijk even zien hoe je een database aanmaakt en de daarbij behorende user toevoegd.

Continue reading