http://communities.vmware.com/community/vmtn/mgmt/vc?view=discussions Most recent forum messages en Tue, 28 Oct 2008 18:55:10 GMT Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/) 2008-10-28T18:55:10Z en http://communities.vmware.com/message/1085945?tstart=0#1085945 <br /> I am currently in the same situation right now. My current plan is the following:<br /> <p /> 1. Stop VC Service.<br /> <p /> 2. Backup VC database on SQL 2000 SP4.<br /> <p /> 3. Restore VC database to SQL 2005.<br /> <p /> 4. Fix SQL logins.<br /> <p /> 5. Set compatibility mode to 2005.<br /> <p /> 6. Recreate SQL jobs for Stats rollup.<br /> <p /> 7. Create a new OBDC Connection with SQL Native Client.<br /> <p /> 8. Update VC Registry entry with new OBDC connection.<br /> <p /> 9. Start VC Service.<br /> <p /> I've already completed these steps on a test VC server, and everything has been working fine. I'll probably leave this running for a week before looking to perform these steps on our production system. I actually performed these steps with VC 2.5U1. Afterwords, I updated to VC 2.5U3. So far, no issues. Tue, 28 Oct 2008 18:55:10 GMT jguidroz http://communities.vmware.com/message/1085945?tstart=0#1085945 2008-10-28T18:55:10Z 1 year, 3 weeks ago http://communities.vmware.com/message/1083811?tstart=0#1083811 Hi,<br /> <br /> Ouch, I don't know why I would have to uninstall VC... VC 2.5u3 is already installed and working perfeclty... Maybo just shutdown the service would be enough ?<br /> <br /> JF Sat, 25 Oct 2008 00:54:39 GMT jfmartin http://communities.vmware.com/message/1083811?tstart=0#1083811 2008-10-25T00:54:39Z 1 year, 1 month ago 1 http://communities.vmware.com/message/1083616?tstart=0#1083616 Well I believe there is a migration path for SQL. Since it's a physical server, you can simply install SQL 2005 SP2 and do an inplace upgrade of the engine. That would work. If it doesn't upgrade, then your only option is to:<br /> <p /> <p /> <p /> 1) dump the data from the current VI database (or do a backup of data only)<br /> <p /> <br /> 2) stop the VC service.<br /> <p /> <br /> 3) install SQL 2005 on that DB server machine, and install SP2, firmware updates, etc.. make sure it's fully patched.<br /> <p /> <br /> 4) uninstall VC and then reinstall (telling the installation that you want to create a NEW DB instance and let it create the DB, and the NEW DB will be blank)<br /> <p /> <br /> 5) import the data from step 1 into the newly created DB. (This is because the schema is different, and you want to just populate the data).<br /> <p /> <br /> 6) start the VC service and verify your cluster / VM's are working. Everything should be good, although you may have to reconnect some machines.<br /> <p /> <br /> With SQL it's a good idea to start with a fresh DB (schema) and import the data back. That should get you where you need to be.<br /> <p /> <br /> Just make sure you backup everything, keep your license keys, configurations, etc.. just in case. Fri, 24 Oct 2008 20:00:31 GMT RParker http://communities.vmware.com/message/1083616?tstart=0#1083616 2008-10-24T20:00:31Z 1 year, 1 month ago 2 http://communities.vmware.com/message/1083470?tstart=0#1083470 Hi,<br /> <br /> We are trying to figure out a plan to upgrade the DB engine on our VirtualCenter server 2.5u3 running SQL Server 2000 SP4. It seems there is now definitive guide to do that. So, does somebody knows how we could do an inplace upgrade of the SQL Server 2000 SP4 DB engine to SQL Server 2005 SP2 ? We want to stay on the same server... so the inplace upgrade of SQL Server is mandatory. Any plan out there ?<br /> <br /> JF Fri, 24 Oct 2008 17:58:34 GMT jfmartin http://communities.vmware.com/message/1083470?tstart=0#1083470 2008-10-24T17:58:34Z 1 year, 1 month ago 3