Migrate SCOM SQL 2012 databases to SCOM 2019, SQL 2019

Tony Strother 171 Reputation points
2021-03-31T17:22:46.61+00:00

Afternoon,

I cannot locate any clear info on this, so thought I would ask.
I would like to use a copy of our SCOM 2012R2, SQL 2012 databases in a new SCOM 2019, SQL 2019 build? That way I do not lose any data in my current environment, which would keep many, many users "happy"..
Is this possible to do??
Appreciate you assistance and time!
Tony

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,413 questions
{count} votes

4 answers

Sort by: Most helpful
  1. CyrAz 5,181 Reputation points
    2021-03-31T19:18:58.283+00:00

    You can't simply "re-attach" a SCOM 2012 database to a SCOM 2019 deployment.
    If you want to keep your data, you need to run an in place upgrade from 2012 to 2016 and then to 2019.
    It you do a side by side upgrade (new SCOM environment alongside the 2012 one), you can't keep your old data. Simple as that.

    0 comments No comments

  2. Tony Strother 171 Reputation points
    2021-03-31T20:06:02.707+00:00

    Thank you for the info!

    0 comments No comments

  3. Tony Strother 171 Reputation points
    2021-04-01T19:57:59.13+00:00

    So after I have done that, could I then build my new SCOM 2019 servers and attach to the database? Our environment is doing away with server 2012R2 so that would have to go.

    Thanks,
    Tony

    0 comments No comments

  4. CyrAz 5,181 Reputation points
    2021-04-01T21:41:36.247+00:00

    No, there is no supported way of "attaching a database from one environment to another", regardless of their version. Neither have I ever seen it documented anywhere.
    Once again, the only supported way to keep your data is to keep your current SCOM 2012 deployment and upgrade it to SCOM 2019.
    You can do that and update your environment to Windows 2019/SQL 2019 in the meantime, but that will require a bit of planification...

    0 comments No comments