Migrating ServiceNow On-Prem DB from MariaDB to PostgreSQL during ITOM implementation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
I am currently implementing ITOM (Discovery and service Mapping) on a Self-Hosted (On-Premises) ServiceNow Instance. The current backend is MariaDB, and we are planning a migration to a different DB engine (considering PostgreSQL).
Given the On-Prem nature of our deployment, I have the following technical questions:
• Migration Risk: Since ITOM creates complex dependencies in the CMDB, is there a risk of data corruption or metadata loss for Patterns and Service Maps during a DB-level migration?
• Database Choice: Is PostgreSQL the recommended alternative for On-Prem environments to ensure better performance for Discovery's high-frequency inserts/updates?
• Workflow Impact: Are there known issues with the MID Server communication or Discovery Probes when the underlying DB architecture changes mid-project?
We are looking for insights from architects who have managed DB migrations in a Self-Hosted ServiceNow environment.