PENDING SCCM Database Update from 2012 R2 SP4 to 2017

[San123]

Dear Team,

Iam having SCCM 2010 in a VM and database in a separate physical server (Windows server 2016 and SQL 2012 SP4).
Now i want to update the database to 2017 for installing SCOM 2019 & SCVMM 2019 as these will not work on SQL 2012 (I need to use one SQL for 3 suites). For this purpose i need to remove SQL 2012 from my current server and install 2017 on the same server. Currently SQL is having only SCCM instance on it.
Iam planning to take the backup of SCCM databse from SQL 2012 and format the server and install SQL 2017 freshly (will give the same server name) and restore the database to 2017 with the same instance name. Will this work ? i need your suggestions. Any other ideas also welcome.

 

[bhethcote]

SQL 2014 can be upgraded directly to SQL 2017 - I just did it (well, to SQL 2019, but 2017 is supported as well) in my customer's environment, they were using a local SQL instance on the site server. There are things you need to do first (See Prajwal's article) - Great article by the way! SSRS is not upgradeable and is a separate download and you'll need to download SSMS v18.8 (I think that's the latest).

On a separate note, that SQL server better be a BEAST! The SCOM IOPS will crush it if it's not.

 

[bhethcote]

Just for some additional info, since both SQL 2012 and SQL 2014 were mentioned, here are the SQL 2017 and SQL 2019 upgrade paths:

SQL Server 2017 (14.x) supports upgrade from the following versions of SQL Server:

• SQL Server 2008 SP4 or later
• SQL Server 2008 R2 SP3 or later
• SQL Server 2012 SP2 or later
• SQL Server 2014 or later
• SQL Server 2016 or later

SQL Server 2019 (15.x) supports upgrade from the following versions of SQL Server:

• SQL Server 2012 (11.x) SP4 or later
• SQL Server 2014 (12.x) SP3 or later
• SQL Server 2016 (13.x) SP2 or later
• SQL Server 2017 (14.x)

 

[San123]

Hi Bhethcote,
Thanks for your time and message.
Iam planning to take the backup of SCCM instance and format the SQL server completely and reinstall the latest OS and SQL 2019 freshly. After this i will restore the SCCM instance to new SQL server. I will use the same servername, instance name and IP address as before.

Will this work ?

 

[bhethcote]

Hi San123,
Yes, it will work, but you'll want to pay really close attention to the SQL Logins and such related to the SCCM server.

Just out of curiosity, are you managing a large amount of endpoints with SCCM and monitoring a good number of devices with SCOM? I've seen similar setups (both good and bad) in the past where both SCCM and SCOM databases reside on a single SQL instance. Conceptually, there's no problem, but in practice, the volume of read/write activity requires a pretty solid, high performance storage setup sitting underneath it. Of course, if it's a really small environment or a lab setup, it won't be as dramatic, but I'd recommend doing a little research on how many total IOPS your setup will produce and size accordingly.

Hope this helps,

BH

 

[San123]

Hi San123,
Yes, it will work, but you'll want to pay really close attention to the SQL Logins and such related to the SCCM server.

Just out of curiosity, are you managing a large amount of endpoints with SCCM and monitoring a good number of devices with SCOM? I've seen similar setups (both good and bad) in the past where both SCCM and SCOM databases reside on a single SQL instance. Conceptually, there's no problem, but in practice, the volume of read/write activity requires a pretty solid, high performance storage setup sitting underneath it. Of course, if it's a really small environment or a lab setup, it won't be as dramatic, but I'd recommend doing a little research on how many total IOPS your setup will produce and size accordingly.

Hope this helps,

BH

Hi Bhethcote,
Thanks for the reply.
Its a small setup of less than 100 users. Actually the SCCM, SCOM, SCVMM using same database but different instances.