Post database Migration Checks

SolarWindNoob

Hey:

We are planning a database migration this week and we went through the knowledge base articles and have got help from support.

What was your experience like
Issues you came across?
Specifics checklist you all have?

Anything that you think people will find useful to make things easier.

ronan.tonilon

As long as you have followed the Database migration guide and made sure all of the polling engines were pointed to the new database location (by running Configuration Wizard of all polling engines), your SolarWinds application should function just like before.

Some checks that you may perform are the following:

• Database checks:
  • Integrity and compatibility checks covered by your DBAs:
    • Run DBCC CHECKDB to ensure no corruption.
    • Verify database compatibility level (adjust to match new version if required).
    • Ensure collation settings match expected configuration.
  • SQL configuration checks:
    • Review SQL Server instance settings (e.g., max memory, parallelism).
    • Check SQL Agent Jobs—status, schedules, and ownership.
    • Validate custom configurations like trace flags or startup parameters.
    • Confirm service accounts are correct and have necessary permissions.
      • Security and access checks:
        • Confirm all logins, users, and roles were migrated and mapped correctly (sp_change_users_login or ALTER USER for orphaned users). Also all and other credentials and their permissions.
        • Validate Windows authentication and SQL authentication logins.
        • Reapply encryption keys or certificates if applicable.
• Services and the SolarWinds application checks:
  • Open SolarWinds Platform Service Manager: Make sure all services are started for all pollers and other scalability engines (HA servers, Additional Web Servers)
  • Orion Web Console:
    • Make sure you can see menu bar, and access all the other pages.
      • Links are functional: (e.g. Click on a node and it routes to the correct node, or what not.)
    • Have all Web Console users check their access. If there are issues, check user permission configuration, open support case as needed if there is still a problem.
    • Check for performance issues. Compare to previous state if it is faster or slower.
  • Verify database connectivity:
    • https://solarwindscore.my.site.com/SuccessCenter/s/article/Verify-the-SQL-and-Orion-server-connectivity-using-the-UDL-file?language=en_US
    • Telnet test, if blocked, use PowerShell and use TestNetConnection.
  • Verify data integrity:
    • Observe data if there are no inconsistency from the last time before migration was done. Check events, audits, alerts, etc.
    • Test alerts: https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-testing-alerts-sw1106.htm
    • Check and test configured Schedules, Jobs, if there are custom tasks like running external programs or what not.
    • Run reports and verify if working properly and compare to previous results prior to migration.
  • Check polling engines:
    • If there are multiple Polling Engines, navigate to Settings > All Settings > Polling Engines. 
      • Review the number of polled elements for each polling engine to ensure they are properly configured and functioning. 
      • Optimize polling engines if needed to ensure optimal performance. 
    • Check node connection to respective polling engines. Test are dependent on polling method used by the nodes.

If issues are encountered, open a support case.

NOTE: This is not a standard checklist, as an experienced SolarWinds support before, this is what I would do and would suggest if asked.

Hope this helps.