Upgrading SCSM 2012 R2 to 2016 and replace Data Warehouse (server or all)

Ingrid_GlatzIngrid_Glatz Customer Adept IT Monkey ✭✭

We're in the planning of upgrading SCSM 2012 R2 to version 2016 including different Cireson products.

Our Data Warehouse Management server is still server 2008 R2 and has an old server name that doesn't match the new naming convention any longer. I know that it's not possible to move the DWH Management server to another server that has a different name, so by upgrading to 2016, I would have to stick to the old name. According to some information, it won't be possible to create a complete new DWH and import all existing data into the new DWH. We need to keep certain information for as long as 10 years. Having 2 different DWH is also not an option.

Does anybody know whether it's possible to insert old DWH data into a new DWH database, contrary to the information I got? Is there possibly another solution to setup a different kind of DWH, import the old data and connect it with the new DWH server? I'm not at all satisfied with the existing SCSM DWH, it's too unstable and needs a lot of effort. SO I'm open for all kind of ideas to upgrade the 2012 R2 environment to 2016 and maybe get a new functioning DWH.

Thanks for your tips.



  • Tom_HendricksTom_Hendricks Customer Ninja IT Monkey ✭✭✭✭
    Without what I consider excessive care and feeding, 2012 R2, 2016, and 1801 would all have been a far cry from functional.  If a mouse sneezes within a 50 mile radius of your servers, the DW jobs will have some sort of cascading failure that will not be resolved until you dig in and re-run everything manually again.  This has been pretty consistent across versions.

    Having said that, I thought that you could restore the DW to a new server, then install a new DW mgt server (or uninstall/install again on same server) with the existing DB's encryption key.  The procedure is here: https://docs.microsoft.com/en-us/system-center/scsm/implement-disaster-recovery?view=sc-sm-1801

    What this article does not cover is the fact that the server names would change.  I invite corrections from everyone else, but I believe this would work (try in a lab first!):

    1. BACK UP YOUR ENCRYPTION KEY if you have not already done so as part of the original install (instructions are in this article, or there is a tool in the install CD for it)
    2. Unregister the data warehouse using either the SCSM console or PowerShell
    3. Upgrade/move/etc. your DW databases to a new server, if desired
    4. Install the DW mgt server following the steps in the article above
    5. Register the new DW mgt server using the SCSM console or PowerShell
  • Ingrid_GlatzIngrid_Glatz Customer Adept IT Monkey ✭✭

    Hi Tom,

    unfortunately, it's hard to find information about not changing the server name for DWH management server. This article here http://aquilaweb.net/2015/05/03/ (first link on the page) has the part that's missing in all other articles "the new server must have the same name as the original server". According to MS, it's the only way, renaming the DWH server is not possible. They've just forgot this important part in all other documentations.

    I actually wanted


  • Geoff_RossGeoff_Ross Cireson Consultant Super IT Monkey ✭✭✭✭✭
    Hi Ingrid,

    You are not the first person ever to experience the pain of DW. It can be very frustrating.

    Firstly, to my knowledge, what you are trying to do including the renaming of the server is NOT possible. Those few articles you can find are correct, that the server must be called the same name.

    Therefore, I wondered if you had considered the option of using Cireson Analytics as your long term archiving solution? Its the complete opposite to DW, super simple to operate but you only get a super simplified set of data. It might not suit your needs but it probably worth investigating. Unlike, DW, you can just inject data right into it via SQL statements so you could pull data from current DW and insert it in to get a continuous record.

    Have a read of my blog here all about it, to get an understanding of what is can and can't do and as always, let me know if you have any questions.

  • Ingrid_GlatzIngrid_Glatz Customer Adept IT Monkey ✭✭

    Hi Geoff,

    we've already considered Cireson Analytics, but it's not what we're looking for in terms of available data. We need to keep user names for as long as 10 years, we need access to Incident action log entries and Service Request action log entries that can be transferred to DWH. The audit feature is necessary, we work in a sensible environment.


  • Tom_HendricksTom_Hendricks Customer Ninja IT Monkey ✭✭✭✭
    I stand corrected then.  It is truly disappointing to hear that renaming is not supported.
  • Adam_DzyackyAdam_Dzyacky Customer Contributor Monkey ✭✭✭✭✭
    Second all the above - DW renaming isn't supported, it doesn't work, and yet it's still a lab scenario I want to go after out my own sheer curiosity as I tend to operate in the mindset that "For every wall there is a ladder." Not quite sure when that kind of lab time will present itself though.

    While it isn't addressing the core of your question and I could be overlooking something here entirely at the very least I'd say extend your DW retention time out to 10 years if you haven't already.

    DW Troubleshooting is certainly a skill in and of itself for sure, but what kind of issues are you running into? Just different jobs failing?
Sign In or Register to comment.