>From Technet: [cid:[email protected]]
Of course, that's just "not supported", vs. won't work. But I've always been the kind of guy to not press my luck. From: [email protected] [mailto:[email protected]] On Behalf Of Marcum, John Sent: Monday, December 14, 2015 8:26 AM To: [email protected] Subject: [mssms] RE: SQL question re: moving Config Mgr to Server 2012 R2 from Server 2008 R2 I was saying that you can restore to a different version of SQL. ________________________________ John Marcum MCITP, MCTS, MCSA Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ [H_Logo] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Monday, December 14, 2015 9:11 AM To: '[email protected]' <[email protected]<mailto:[email protected]>> Subject: [mssms] RE: SQL question re: moving Config Mgr to Server 2012 R2 from Server 2008 R2 You can't restore to a different version of SQL. So, you either upgrade the source server first, or you upgrade the destination server after. I think John was saying to do that latter. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mote, Todd Sent: Friday, December 11, 2015 10:37 AM To: '[email protected]' Subject: [mssms] RE: SQL question re: moving Config Mgr to Server 2012 R2 from Server 2008 R2 Only reason I do is to make sure that SCCM knows about the SQL change rather than restoring a database from an older version of SQL into a newer version of SQL after the fact. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Friday, December 11, 2015 8:57 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: SQL question re: moving Config Mgr to Server 2012 R2 from Server 2008 R2 I wouldn't bother upgrading SQL first. ________________________________ John Marcum MCITP, MCTS, MCSA Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ [H_Logo] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mote, Todd Sent: Friday, December 11, 2015 7:44 AM To: '[email protected]' <[email protected]<mailto:[email protected]>> Subject: [mssms] RE: SQL question re: moving Config Mgr to Server 2012 R2 from Server 2008 R2 I would upgrade the SQL version first, make sure everything is running correctly, do an SCCM backup, then on your new VM install the same version of SQL you upgraded to on the old server and install the same CM version, then do a site restore. All the way at the bottom of the Supported Configurations TechNet article is the upgrade info. https://technet.microsoft.com/en-us/library/gg682077.aspx Todd Upgrade to SQL Server 2014 When your version of Configuration Manager supports SQL Server 2014, Configuration Manager supports the in-place upgrade of SQL Server to SQL Server 2014 with the following limitations: * Each Configuration Manager site must run a version of Configuration Manager that supports using SQL Server 2014 before you can upgrade to SQL Server 2014 at any site. * When you upgrade the version of SQL Server that hosts the site database at each site to SQL Server 2014, you must upgrade the SQL Server version that is used at sites in the following order: * Upgrade SQL Server at the central administration site first. * Upgrade secondary sites before you upgrade a secondary sites parent primary site. * Upgrade parent primary sites last. This includes both child primary sites that report to a central administration site, and stand-alone primary sites that are the top-level site of a hierarchy. [System_CAPS_important]Important Although you upgrade the service pack version of a Configuration Manager site by upgrading the top-tier site first and then upgrading down the hierarchy, when you upgrade SQL Server to SQL Server 2012, you must use this sequence, upgrading the primary sites last. This does not apply to upgrades of SQL Server 2008 to SQL Server 2008 R2. To upgrade SQL Server on the site database server<javascript:void(0)> ________________________________ 1. Stop all Configuration Manager services at the site. 2. Upgrade SQL Server to a supported version. 3. Restart the Configuration Manager services. [System_CAPS_note]Note When you change the SQL Server edition in use at the central administration site from a Standard edition to either a Datacenter or Enterprise edition, the database partition that limits the number of clients the hierarchy supports does not change. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Johns, Damon (DoJ) Sent: Friday, December 11, 2015 1:44 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] SQL question re: moving Config Mgr to Server 2012 R2 from Server 2008 R2 Hi Everyone, Hoping I can get some clarification on this. I'm looking to move my physical Config Mgr 2012 R2 SP1 CU2 site running on Server 2008 R2 to a new Server 2012 R2 VM next year. I'm across how to achieve this however I do a question about SQL versions. Presently my Server 2008 R2 Config Mgr instance is running on SQL 2008 R2. I want to use SQL 2014 (or latest supported version next year) on my new Sever 2012 R2 Config Mgr instance. What is the best way to achieve this as part of the overall process? Cheers Damon ________________________________ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
