Migrate DPA Application and Repository to Windows Server 2022/SQL 2022

Hello! 

We are looking to migrate all things Solarwinds to 2022.  I wanted see if anything has changed in 4+ years. 

https://thwack.solarwinds.com/product-forums/database-performance-analyzer-dpa/f/forum/10727/moving-dpa-repository-to-new-sql-server

Currently monitoring up to 100 databases, some Azure, and also use the VM Option. 

Thanks!

Dave

Parents
  • Only DPA 2023.2.1  supports SQL Server 2022 either for monitoring or for use as the DPA Repository as well as one of its new authentication options to use Azure AD.

    Follow the guidelines in the DPA Install and Upgrade Guide for 2023.2.1

    Depending on how old your DPA version is that you need to upgrade from, you may have to first upgrade to an interim version which 2023.2.1 supports direct upgrades from.

    Note that you can only connect to SQL Server 2022 using the new 12.2 Microsoft JDBC Driver that ships included in the DPA 2023.2.1 release.  However, that new MS Driver is not always backward compatible with all earlier non-default MS JDBC connection options that you may have specified in the prior monitored and SQL Server repository DB connections. 

    For example, the new MS driver ONLY supports encrypted communication. If your prior options specified things like Force Encryption=NO or set SSL mode=Disabled, upon upgrading to 2023.2.1 or later, the new MS driver may not allow connections to those any longer until you use the defaults or change those options to Force Encryption=YES and/or do not disable SSL mode.  If you absolutely don't want to use encrypted communication to some of your older SQL Server databases, your only other option is to override the JDBC driver choice to use the older JTDS for those SQL Server instances while retaining the MS driver option to connect to SQL Server 2022 and later.

    As far as Azure and VMWare monitoring, those are still supported. The following is the DPA 2023.2.1 supported DB type and cloud variants of DB types monitored for analysis or for use as a DPA Repository.  

    Below is the current supported DB types and cloud variants supported by DPA 2023.2.1

  • What about hardware requirements?  We recently did some changes to CPU and RAM on our current DPA deployment.  Do these change at all with Server and SQL 2022?

  • Hard to say with SQL Server 2022, you'll need to review if Microsoft indicates their requirements are bumped up (especially if 2022 will be self-hosted instead of an Azure Cloud VM that you can adjust resources if needed.

    I don't believe there are additional resources required between 2023.1 and 2023.2. However, depending on what release you upgraded from to 2023.1, some of the enhancements done in the last couple of years (notably, FindSQL and the Index Tuning Advisor) bumped up resource needs. If you are resizing resources, I'd personally go with a bit more than what is specified in the install guide resource requirements. We're looking into revising those and they probably need to be adjusted a little higher. But if you are running fine and have enough head room during the day and no conflicts during the nightly analysis jobs on 2023.1, 2023.2 shouldn't be any different.

Reply
  • Hard to say with SQL Server 2022, you'll need to review if Microsoft indicates their requirements are bumped up (especially if 2022 will be self-hosted instead of an Azure Cloud VM that you can adjust resources if needed.

    I don't believe there are additional resources required between 2023.1 and 2023.2. However, depending on what release you upgraded from to 2023.1, some of the enhancements done in the last couple of years (notably, FindSQL and the Index Tuning Advisor) bumped up resource needs. If you are resizing resources, I'd personally go with a bit more than what is specified in the install guide resource requirements. We're looking into revising those and they probably need to be adjusted a little higher. But if you are running fine and have enough head room during the day and no conflicts during the nightly analysis jobs on 2023.1, 2023.2 shouldn't be any different.

Children
No Data