TMS 13.2.2 - SQL 2005 to SQL 2008 migration

Similar Questions

• TMS SQL 2005 DB to SQL 2008

  Hello

  I have here a nice problem. We had a former TMS (v.13.1) Server installed to MS 2003 R2 with SQL 2005.

  The export of the DB has been problem free.

  Now, we need to upgrade the operating system to MS 2008 R2 64 bit. We had installed the TMS Version 13.1.2 with SQL 2008.

  How can I import the old DB for new MSDS?

  Who has an idea or if it is?

  Greetings

  Jens Lantermann

  Ditto on what Martin says with regard to the questions of Justin

• SQL 2005 to SQL 2008 R2 update

  Hey everybody,

  I have a MSD (13.0) running on a dedicated Windows 2003 server and has the database hosted on one of our corporate servers running SQL 2005. All the companies getting SQL servers migrate to 2008 R2 at the end of the summer. Has anyone done this type of migration with the MSDS database and what questions or unexpected came?

  Thank you

  Hello Steven

  I'm assuming that you'll upgrade TMS to the latest version as well (13.2%).

  Longer if you follow the procedure documentation and check all the prerequisites and requirement conditions everything should go smooth.

  Please check this link, in particular page 16:

  http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/TMS/Install_Guide/Cisco_TMS_install_guide_13-2.PDF

  Also, I highly recommend to install TMSPE that uses the database SQL instead of the OpenDS.

  http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/tmspe/Install_Guide/Cisco_TMSPE_Deployment_Guide_1-0.PDF

  Please note that you must upgrade your VCS so at least 7.1.

  I hope this helps.

  Rafal

• 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

• TMS supports always on SQL?

  According to the title of the thread, can someone tell me if the TMS supports the SQL feature "always there"?

  I don't know much, but our DB guys want to know.

  My understanding is that the "Always On" function is part of SQL 2012 and 2014 SQL.

  TMS is currently only supported on SQL 2005 or SQL 2008 (but supports for 2005 is to be removed in a future version of TMS - see the release notes for the latest version).

  Wayne

  --

  Remember the frequency responses and mark your question as answered as appropriate.

• 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 on vOrchestrator on SQL 2005 and SQL 2008?

  I was reading the support for vCenter and vOrchestrator matrix and was surprised to see that vCenter is fully supported on SQL 2008 but vOrchestrator is only supported on SQL 2005. As we all migrate to SQL 2008, we want to install as many vSPhere on SQL 2008 as possible. Is - it possible/decision-making supported to install vSphere on SQL 2008 and then separately install vOrchestrator on SQL 2005? Installing vCenter it seems to me that if both components have been installed at the same time, but maybe it was because I was in a lab environment and went with the built-in SQL Express.

  Any word on what vOrchestrator will support SQL 2008? I really don't like VMware may not have common requirements for all their products. I know that vOrchestorator was an acquisition, but still... come on people! Life is complicated enough.

  vCenter and Orchestrator use their own databases, you can install vCenter on SQL 2008 and Orchestrator 2005 without problem.

  ---

  VMware vExpert 2009

  http://blog.vadmin.ru

• Ms SQL Server 2005 to Oracle 9i migration

  Hi all
  
  MS-SQLServer to Oracle 9i migration. in migration, work bench lists only SQL SERVER 2000
  
  Thank you
  -
  ABK

  Oracle Migration Workbench is outdated and replaced with SQL Developer Migration Workbench.
  Take a look on:
  http://www.Oracle.com/technology/tech/Migration/Workbench/index_sqldev_omwb.html

• The installer of SQL 2008 R2 - I get could not open key: UNKNOWN\Components\C89F41A0CA86

  I'm trying to install SQL 2008 R2 on a Windows Server 2008 computer. There a SQL 2005 and 2008 R2 installed before.
  I uninstalled everything about SQL using the Add/Remove Programs, CCleaner and Windows Installer cleaner.
  I'm under SQLEXPRWT_x64_ENU.exe (date of Monday, April 5, 2010 09:29:28) I downloaded from Microsoft. I unlocked the file, I am logged in as an administrator and I run as administrator.
  I get
  The following error occurred:
  Could not open key: UNKNOWN\Components\43C313DB6EBAD154F901C6B5BFA69F06\C2BF01D69A282F04190DB76EC40FAD2F.   Check that you have sufficient access to that key or contact your support team.
  Another window shows:
  Description:
  SQL Server 2008 R2 Setup has encountered an error.

  Signature of the problem:
  Problem event name: SQL100MSI
  Signature of the problem 01: 10.50.1600.1
  Signature of the problem 02: 10.50.1600.1
  Signature of the problem 03: SqlSupport.msi
  Signature of the problem 04: 0xE1C5DEF0
  Signature of the 05:1402 problem
  Signature of the 06 problem: Install_SqlSupport
  OS version: 6.0.6002.2.2.0.272.7
  Locale ID: 1033

  More information about the problem:
  LCID: 1033

  It occurs during the installation of Support files, ExecuteStandardTimingsWorkflow.

  Someone at - it ideas?
  Thank you
  Deb

  Hi Deb,

  Your SQL 2008 R2 issue is more complex than what is generally answered in the Microsoft Answers forums. It is better suited for the IT Pro TechNet public. Please post your question in the SQL Server Forum. You can follow the link to your question:
  http://social.technet.Microsoft.com/forums/en-us/category/SQLServer

• 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

• SQL 2008 R2?

  Anyone running vCenter 4.0 U1 against SQL 2008 R2? I tried to make the switch last night with no luck. I want to do this so that we can go off the power for the installation of SQL SERVER 2005 Express, before moving on to 4.1.

  Any input would be much appreciated!

  not compatible for a DB vCenter

  VMware vSphere compatibility matrices

• 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

• LCM on SQL 2008?

  You can run LCM on 2008 and is supported or when it will support.

  Anyone know?

  The following data types are supported by Orchestrator that is used by LCM:

  Microsoft SQL Server 2005 Enterprise (SP2)

  Microsoft SQL Server 2005 Enterprise (SP2) x 64

  Microsoft SQL Server 2005 Enterprise (SP1)

  Microsoft SQL Server 2005 (SP2) Standard

  Microsoft SQL Server 2005 Standard (SP1)

  Microsoft SQL Server 2000 (SP4) Enterprise

  Microsoft SQL Server 2000 (SP4) Standard

  Oracle 10g Release 2 (10.2.0.3.0) Enterprise x 64

  Oracle 10g Release 2 (10.2.0.3.0) Enterprise x 32

  SQL 2008 will be added once it has been tested.

  That said, I think it works, so give it a try and let us know if you have any questions