vCenter database for SQL 2008 recommendations

Similar Questions

• Large building VM for SQL 2008 Enterprise

  I was counting on the construction of a large environment of virtual machines for SQL 2008 Enterprise Edition.  Only, I realized that the maximum number of vCPUs, that you can assign to a virtual machine is based on this document 8:

  http://www.VMware.com/PDF/vSphere4/R41/vsp_41_config_max.PDF

  If I understand each vCPU corresponds directly to a single core on the physical processors.  This in turn means that maximum processing capacity that I can get to a single virtual machine is the equivalent of 2 x quad core processors (8 cores = 8 vCPU) or is there another way to work so that I can get more than that?

  I am concerned about this environment specific SQL, which need processing more than 8 cores/vCPUs.

  Ideas?  Or what I need to take this out of VMware environment and deploy physics?

  No. 8 is the maximum number of vCPUs, that you can assign to a virtual machine - as much as VMware would like to say that all the workloads can be virtualized it is those out there who might not be able be good candidates for virtualization and, possibly, your SQL server server can be one of these. That being said, in my experience, I did not fall on many SQL servers that cannot not virtualized.

  What makes you say that thei SQL server needs more 8 cores?

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Change Vcenter DSN 2005 SQL native client for SQL 2008 native client

  Hi all.

  I tried to upgrade our Vsphere for VM Windows 5.5 to Vsphere 6.0 for Windows (latest version of January).

  The upgrade checking failed after entering the credentials of user Vcenter. The error is 'unsupported database driver.

  In fact the DSN connection uses the SQL native client 2005.90.2047. Is also on the system SQL native client 10. (Version 2009.100.2500) is installed. I think it's the SQL 2008 R2 native client.

  The SQL Vcenter database is on a remote database SQL 2008 R2 server.

  I tried to change the DSN of SQL native client 10. The service started, but I've seen lots of SQL errors in the vpxd.log. I could solve only to return to the snapshot and restore the SQL database.

  How can I change the SQL Native client to connect DSN correctly?

  Thank you very much in advance?

  Edy

  Have you removed the old DSN entry and created a new using the driver of the new (and good)? And have you checked the registry if your change reflected here (\VMware Virtualcenter\DB HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.)?

• Migrating from a SQL Express 2005 local database to SQL 2008

  I was reading up to the migration of the "shipped" vCetner 4.1 to a database SQL 2008 database external recently and came across these two articles VMWare KB:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1028601

  and

  http://KB.VMware.com/selfservice/documentLinkInt.do?micrositeID= & Popup = true & LanguageID = & externalId = 7960893

  The difference I see with these is that you have just to back up the database, import, reinstall vCenter, while the other has you just stop vCenter, migrate the database and re-create the rollup SQL Agent jobs. What article we should be followed? Both? Just the first one will be?

  Thanks for any input you can provide!

  -Brian

  Since MSSQL 2005 Express does not have the SQL agent, vCenter Server manages the hourly job.

  Switch to MSSQL 2008 Edition nonExpress would require for you allows you to deploy the necessary jobs.

  So, my suggestion is to use http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1028601 with a small change:

  After step 7. (there is a lack 8. you'll have 'implement' :-)) you must deploy the jobs described in http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1029824 (section 1))

• vCenter database using SQL Express Edition

  VMware dear Experts,

  If I use the following sql express edition for vCenter database, so I would like to know what will be the maximum size of vCenter database and host how much we can add in vCenter server.

  SQL express edition 2000 32/64 bit

  SQL express edition 2005 32/64 bit

  SQL express edition 2008 32/64 bit

  SQL express edition 2012 32/64 bit

  Concerning

  Mr. VMware

  The limitation is NOT on the number of hosts or VMs. SQL limitation only based on size.

  SQL Express 2005/2008 - 4 GB

  SQL Express 2008 R2 to 10 GB

  SQL Express 2012 to 10 GB

• VCenter on MS SQL 2008 R2 installation

  Hello

  I can't install vCenter (4.1 Update 1).

  I installed a basic MS SQL Server R2 on a Windows Server 2008 R2.

  Installing vCenter I block at the choice of the database level.

  He therefore asks me if I want to use a 2005 Express version or a database of existing support. So I choose the second option, but it offers me nothing in the drop-down list (DSN).

  When I enter the name of the previously created DSN (via the control panel > administrative tools > Data Source (ODBC)), I have an error message "the DSN"xxx"does not exist or is not a 64-bit system DSN. vCenter Server requires a 64-bit system DSN. »

  1 - remember to install the client SQL 2008 R2 on the vCenter

  2 good create a "System DSN" and not UN "user DSN".

  3. to install at least a vCenter 4.1 (en 4.0 go looking for ODBC administration in SysWOW64)

  Eric

• Database Microsoft SQL Server recommended recovery mode

  I've seen a few articles about MS SQL Server recovery models and the effect it has on the file log and its growth, but not where I see which is the recommended setting should be creating the database for installation.

  Is there a recommended recovery model setting?

  Is it necessary to try to recover the last full backup of database transactions?

  Thanks in advance.

  David.

  use the Simple Mode

  a couple of other things to keep on hand

  http://www.VMware.com/resources/TechResources/1025

  http://KB.VMware.com/kb/1003980

  http://KB.VMware.com/kb/1025914

• vCenter 4.1 & SQL 2008 R2

  I try to install vCenter 4.1.0 - 259021 on my new Server Windows 2008 R2 standard and SQL 2008 R2 Express 64 bit (build 10.50.1600)

  Is this a supported VMware platform? (no trace on vsp_compatibility_matrix.pdf)

  Thanks for help

  Mauro

  The OS is fine.

  But also check compatibility (page 12) DB.

  The ony SQL Express that is supported is the 2005 version.

  And SQL Server 2008 R2 is not supported at all, in fact. Only 2008 and 2005 versions.

  André

• How config VM for SQL 2008?

  I'm under ESXi 4 on a Dell of 710 on the SDCard with Raid 10. I have 12 GB of ram (soon to go to 48 since this server was going to be something else) with double Quad-cores. I am running WSUS as a virtual machine and SQL 2008 all 64 bits but uses SQL to the time as a virtual processor. All this in the same data store. I have an another data store on the same server and these 2 drives are Raid 1, but I have not yet used. Everything is contained in a box and will always be like that.

  1 can be located the SQL and the virtual machines with the help of it in the same data store or leave I better to put on various Raids?

  2. I want to add Sharepoint which uses also SQL 2008, if it was another instance of SQL2008?

  3. the amount of ram (assuming I'm 48 concerts) and the number of processors should I call?

  Thank you

  Gary

  Gary,

  without knowing what we take on the workload, it is not easy to answer your questions.

  However, we will try to find answers for you.

  Material:

  S ' ensure that your hardware is listed on the HCL. (Server, RAID controller,...)

  -For optimal performance, you must use SAS HDD and battery backup cache writing. Write cache - in my opinion - is essential!

  Licensing:

  -You can save or lose a lot of money thanks to a license.

  -With 1 license of Windows Server Enterprise (2003R2 plus) MS grants you the right for up to 4 virtual machines on 1 physical server.

  -SQL2008 to take a look at the millisecond of license. Depending on the version, you will need to purchase a license by vCPU.

  Installation:

  -Make sure you configure your data warehouses VMFS with the size of the desired block (1-8MB) for the maximum size of VMDK you expect.

  -If you use Windows 2003 server, be sure to align the partitions of the virtual machine!

  -Best practices for reading MS for SQL installations. (Alignment, partition NTFS block size,...)

  Now we will answer your questions:

  1.) depending on the workload and the SQL recovery mode (base, in bulk, plenty) it may make sense to have vmdk on different logical drives (spindles). With the hardware you have I recommend you to create up to 3 virtual drives (OS, data SQL, transaction logs). Put the OS and data on the RAID10 and newspapers on the RAID1.

  2.) well, again it depends on the workload. If a SQL Server is not enough you can save the money for a second license of SQL.

  3.) recommended is to assign as many vCPU and as much RAM as you need. You can always adjust the settings if necessary thereafter. Remember SQL server licenses when adding additional vCPUs.

  André

  PS: I personally do not trust SD cards with the exception of my camera. I always install ESX (i) on the HARD disk!

• Leaving the vCenter, database SQL 2008 R2 to SQL 2012 R2

  Hi guys,.

  I have a project to move our of vCenter company database in SQL 2008 R2 Cluster at our new farm of R2 SQL 2012, is it as simple as:

  1. backup of database

  2 restore database in SQL 2012 R2

  3. set up new DSN (SQL Native 11 for 2012 R2?) pointing to vCenter server

  OR is there more to him because of the differences between SQL 2008 R2 and SQL 2012 R2?

  PL, refer following links: -.

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=7960893

  or even more plus easy & accurate steps are here:-

  Migration of database SQL Server of VMware vCenter. vDestination: you & #039; Re almost there

• Configuration of SQL 2008 R2, Enterprise Edition for vCenter Server 5.1

  Greetings to all seasons.

  Kind of a newbie here. That's my lab environment.

  I have always used the vCenter Server install Simple option that also installs the shipped Microsoft SQL 2008 R2 Express edition.

  Now, I do an eval of vSphere 5.1 and I want to manually configure a database server using the Microsoft SQL 2008 R2 Enterprise Edition.

  I know how to install the database server and it works. But I do not know how exactly set up a database for vCenter Server.

  I looked at the guide Configuration / Installation of vSphere and I don't seem to be able to follow the preparation vCenter Server databases section, because I'm not a person to the database. Y at - it any other guide or a blog, I can follow? I searched a lot and found everything I was looking for. Thought I would ask here.

  Here are the virtual machines I have.

  Lab - DC1 (domain controller)

  Lab - DC2 (domain controller)

  Lab-SQL1 (SQL 2008 R2, Enterprise Edition)

  Lab-SQL2 (SQL 2008 R2 Enterprise - subsequently configure failover clustering)

  Lab-VC1(vCenter Server 1)

  Any help is appreciated!

  Happy holidays.  Here is a link to another site with a nice installation guide for SQL 2008 for VMware.  Version 4.x, published in lonesysadmin.net was very helpful, so I'm sure that the 5.x update (have not read through it again) must be all too packed with useful tips.

  http://lonesysadmin.NET/2011/10/06/how-to-install-Microsoft-SQL-Server-2008-R2-for-VMware-vCenter-5/

• Best database for vCenter Server 4

  I was wondering what would be the best recommendation for vCenter database server SQL 2005 Enterprise or Standard 64-bit or 32 or 64-bit SQL 2008 Standard or Enterprise. I am trying to build a benefits and disadvantages. I have the database compatibility matrix, but I wondered about the characteristics that could give vCenter that it may not have the capacity. SQL 2008 gives any advantage that 2005 is not that someone has seen or knows. I just want to understand the best database to go with any information about this would be very useful to make my decision. I have difficulties to find advantages and disadvantages to decide what data to go with vCenter

  Hello

  in my opinion, it depends on your deployment, at the present time that I deployed SQL Server 2008 and use with my VCenter 4 so far it was good my environment is relatively low 88 VMs, it's the configuration I use:

  SQL Server 2008 SP1 STD x 64

  Windows Server 2003 R2 SP2 x 64 STD

  I did not notice my old previous deployment if performance:

  SQL Server 2005 STD x 86 SP3

  Windows Server 2003 R2 SP2 STD x 86

  back then my environment was still 35 VMs

  Kind regards

  AWT

• VCenter 4.1 install error on a french MS SQL 2008 SP1

  Hi, we have a problem with a windows 2008 R2 (US or EN) and a MS SQL 2008 EN SP1.

  We cannot install the vcenter server. We have an error "Error 25003. Installation failed to create the repository of the vCenter server. »

  It works with MS SQL Express 2005 or 2008 US.

  It also works with a MS SQL 2008 SP1 US.

  That's OK with a MS SQL 2008 SP1 EN when we install a vcenter 4.0 Update 1.

  We have another problem:

  We cannot account system choice when we install Vcenter 4.1 with a DSN for SQL 2008, even when we turn off the UAC.

  Kind regards.

  Xavier

  PS: Here is the error in the windows event viewer:

  Log name: Application

  Source: VMware VirtualCenter Server

  Date: 2010-07-21 15:22:14

  Event ID: 1000

  Task category: no

  Level: error

  Keywords: Classic

  User: n/a

  Computer: VCENTER

  Description:

  The description of event ID 1000 in the source VMware VirtualCenter Server is not found. The component that triggered the event is not installed on the local computer or the installation is corrupted. You can install or repair the component on the local computer.

  If the 'event originated on another computer, the information display must be registered with l' event.

  The following were included with the event:

  A database error: "ODBC error: (22007) - Microsoft . http://SQL Server Native Client 10.0SQL ServerLa a type conversion of varchar to datetime data type data has created an out of range value. "is returned when you run the SQL statement" "

  INSERT INTO VPX_LIC_METADATA (LAST_SAMPLE_ID, LAST_SAMPLE_TIMESTAMP, RETAINED_SAMPLE_ID, RETAINED_SAMPLE_TIMESTAMP, GLOBAL_DIGEST, IS_STATE_VALID, WEEK_KEEP_COUNT)

  "VALUES (0, ' 1900-12-31 00:00:00 ', 0, ' 1900-12-31 00:00:00 ', NULL, 1, 208).

  The message resource is present but the message is not in the table of chains or messages

  The event XML:

  PS2: error in the vpxd.log

  Section of VMware VirtualCenter, pid = 616, version = version 4.1.0 build-258902 = option = exit

  Current working directory: C:\Windows\system32

  Log path: C:\ProgramData\VMware\VMware VirtualCenter\Logs

  Initializing the SSL

  Using the libcrypto, version 9080CF

  Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000

  A database error occurred: "ODBC error: (22007) - [http://SQL Server Native Client 10.0 | ]. http://SQL Server Native Client 10.0] [SQL Server] One of the type conversion of varchar to datetime data type data has created an out of range value. "is returned when you run the SQL statement" "

  INSERT INTO VPX_LIC_METADATA (LAST_SAMPLE_ID, LAST_SAMPLE_TIMESTAMP, RETAINED_SAMPLE_ID, RETAINED_SAMPLE_TIMESTAMP, GLOBAL_DIGEST, IS_STATE_VALID, WEEK_KEEP_COUNT)

  "VALUES (0, ' 1900-12-31 00:00:00 ', 0, ' 1900-12-31 00:00:00 ', NULL, 1, 208).

  Is not init tableDef object: Vdb instance is not initialized or is fired

  Failed to initialize LDAP backup

  Xavier, I got the same error (with German SQL Srv).

  I have changend a few values in the DSN configuration:

  • change the language of the system for English messages

  • Uncheck the perform Translation for character data

  • Uncheck the use regional settings when out currency, numbers, Dates, times and

  After that, I installed successfully vSphere 4.1 server.

  Kind regards

  Andreas

• vCenter database disk space

  Hello

  We have vcenter database (SQL 2005) on a computer separate virtual as the vcenter server. Vcenter database drive currently has 1.5 GB of available space.

  What is the best way to ensure that we are not running out of disk space on the unit containing the vcenter database?

  Thank you

  assuming that your DB is not on the system (c) partition, but rather on a separate data partition, you can use Windows diskpart to extend the volume without interruption to the BONE.

  Can we assume that the VM SQL has different HARD drives that are presented to each volume in the operating system?  If so, you can increase the size of the HARD drive in the vSphere Client, then run diskpart in the volume in the operating system.

  Also, see the bottom of discussion for some good advice on preserving the health of your VCDB

  Database Microsoft SQL Server recommended recovery mode

• SQL 2008 sp1 support?

  Does anyone know if sp1 for SQL 2008 is still supported?

  I checked and don't see it listed in the compatibility matrix, but thought I'd ask just in case.

  Thank you.

  FYI ANY version of a database will be supported.  If she supports SQL 2008 ALL future updates SP1, SP2, etc... will be supported, if that's what you're asking... SQL 2008 is on the list but not SP1.

  If there are major changes, which would be 2010 SQL (or other).  Service Packs are supposed to be included.