vCenter on vOrchestrator on SQL 2005 and SQL 2008?

Similar Questions

• 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

• 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.)?

• vCenter 4.1 on SQL 2005 express upgrade to vc5

  Hello

  Am looking for first upgrade our environment for vsphere 5... first step is to vcenter.  I've read a lot of threads on this topic... but each looks different... Some say to database backup and uninstall it all... others suggest upgrading the database to 2008 r2 first, etc.

  VSphere 5 has been out for several months, this is a generally accepted approach for upgrading to vcenter 4.1 to 5 located on 2005 express?

  My configuration:
  -vcenter installed on 64-bit Windows 2008 R2

  -The 32 bit SQL 2005 express database

  -You are looking at using SQL 2008 R2 express as database

  -Looking at on place upgraded on the same server 64-bit currently in

  All advice appreciated.

  ilyo - I just made this update even 2 weeks ago.  See the process I followed here:

  http://communities.VMware.com/thread/393923

  It will be useful.

  Wally

• SQL server 2005 and 2008

  I had SQL server 2005 and 2008 running on windows XP Professional SP3 PC but uninstalled mistakely version 2005. Now I try to install it back, but I get the error message that my WMI configuration does not allow it.  What should I do to fix this?

  ASK THE QUESTION IN THE SQL SERVER FORUM:
  http://social.msdn.Microsoft.com/forums/en/category/SQLServer

• 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 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

• 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é

• 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

• OLEDB connection to sql server 2005 using ssis 2008 problem

  Hello

  I'm trying to create the oledb connection to sql server 2005 to help using ssis 2008.

  But I get an error message "cannot generate SSPI context".

  More information: -.

  Using SSMS, I can connect to sql server 2005 and the network protocol option, I have to choose is "NamedPipes".

  Are there special properties that I need to put everything in creating some oleb connection via ssis 2008.

  Please help as I am not able to find a solution on technical Web sites.

  I changed the connection oledb connection string.

  Name additional SPN, which is the same as the name of the server and it worked.

• TMS and SQL 2008 R2

  Hi all

  We plan to spend our SQL 2005 a 2008R2 server. In the Installation of TMS and Quick Start Guide (http://www.cisco.com/en/US/docs/telepresence/infrastructure/tms/install_guide/Cisco_TMS_Install_Getting_Started_Guide_13-1.pdf , page 6), they say that all versions of SQL 2008 are supported, but we must be sure that this includes the SQL 2008R2. Are there restrictions or considerations?

  Thank you!

  I seem to TMS doesn't run well with SQL 2008 R2 no problem

• Great migrations: move from vCenter 5.1 on Windows 2008R2/SQL 2008 5.1 or 5.5 on 2012 2012 Windows/SQL

  In anticipation of the end of mainstream support for Windows Server 2008 R2, I want to migrate an installation vCenter to a whole new server and MS SQL Server.

  It is a virtual machine running in my host cluster. There Server vCenter Update Manager, Converter Standalone and some services not VMware that I can handle it myself. ADAM is installed as part of the vCenter Server requirements, and it is also attached to an AD domain where I use AD, single sign - on.

  The host cluster is four 5.1 ESXi hosts that are up to date, and helped HA and DRS. They use also switches distributed to all of their network connectivity, including vMotion, management, fault tolerance (although I do not use FT) and virtual machines.

  I did upgrades on-site to vCenter before and I replaced SQL Express with SQL Standard on the same server, but I did not move before vCenter. I'd make some drastic measures, as I understand:

  * Complete backups (of course) of SQL in the server itself, ADAM

  Installation of a new server operating system and SQL 2012

  Withdrawal of databases and reinstall them on the new server

  * Restoration of ADAM on the new server

  Installation vCenter, Update Manager, etc.

  * Hoping the host cluster is mounted on the new server, and nothing breaks

  I'm not all that worried about maintaining statistics, so maybe it is possible to install a new server vCenter Server and simply move the host cluster from the old server to the new. I moved one vCenter to another host, but that was before I put in place of distributed switching.
  --

  I found this on a related post:

  Migration in a new vCenter VMware environment. IT diversifies

  This manual seems to echo what I've read so far, I had to disassemble the distributed switches until I can migrate any host to a new server vCenter. Yuck. Well, I've migrated from the standard to the switches distributed without downtime before, so I can do the opposite.

  --

• 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/

• Local SQL database migration from Vcenter 5 to a SQL cluster

  Hello

  I'm trying to migrate my real installation vcenter 5 with a sql local database to a SQL clusster.

  This is manipulation that I do:

  -Stop services vcenter

  -Copy the mdf and ldf for the database files in my directory my SQL cluster

  -Change the ODBC connector to specify the path of the database news

  After this manipulation I try to restart services Vcenter and he pop up me an error.

  After somes tests I do an unistall of the vcenter instance.

  I have check the ODBC connector after unistall and it has been deleted.

  I create another with the pathof my database to my SQL cluster and I restart installing Vcenter 5

  When I check "use an existing database" and specify my recreate ODBC connector before.

  Installation works very well.

  After restarting my server vcenter server start without problems and work.

  I need to know if there is a possibility of just 'fix' the instance to specify the new database because uninstall the instance is a great action?

  Thanks for help you,

  Hello

  I have try this manipulation in the laboratory environment and this work as a result of this step:

  -Copy the files mdf and listening to your new location of the database database

  -Unistall Vcenter Server on your server

  -Remove the ODBC if not erased by installation

  -Create it again with the new location of the database

  -Restart installing Vcenter Server and specify "use an existing database" and refer to the ODBC connector create just before

  -To complete the installation and launch your Vcenter

  Attention I have try this experiment with a 5 Vcenter environment.

  I don't know if it works with 5.1

• vCenter database for SQL 2008 recommendations

  (1) databases of vCenter 2.5 runs on SQL 2008?

  (2) vCenter 4 databases will work on SQL 2008?

  I have searched 2.5 vCenter database requirements and come up empty.  Does anyone know if VMware supports SQL 2008?

  I'd start on page 71 of the http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_vc_installation_guide.pdf

  Rick Blythe

  Social media specialist

  VMware Inc.

  http://Twitter.com/vmwarecares

  http://Twitter.com/vmwarekb