ServiceNow RaptorDB Migration Frequently Asked Questions

[Harneet Sital]

Q: How many variants of RaptorDB are currently out there?

A: Currently we have two variants available for customers - Standard and Pro which has different 

Q: Do I need to do sub prod testing?
A: ServiceNow Engineering will recommend sub prod testing if your instance profile meets testing recommendation criteria.

Q: Will ServiceNow do additional testing of my instance/load?
A: ServiceNow testing of the database and application layer compatibility has been ongoing since 2022. Customer specific testing (large, complex and customized sub prod instances and production load testing) has been ongoing since 2023. Additional customer specific testing will be determined by ServiceNow engineering on a case-by-case basis.

Q: Do I need to do anything differently after migrating to RaptorDB?
A: No, everything at the application layer (applications, integrations, customizations, tables, queries) will be the same before and after the migration. The database is transparent to the customer/end users.

Q: Can I/should I start following different platform or database management best practices after migration?
A: No, all guidance on Platform and database best practices are the same.

Q: What happens if there is a failure in the migration process?
A: ServiceNow will cancel or fail the migration before cutting over to the new database, depending on when the failure occurs, and your instance will remain on MariaDB until the issue is resolved and migration cutover is rescheduled.

Q: What if there is a failure after I am on the new database?
A: ServiceNow follows a “fix forward” strategy and will escalate to resolve all RaptorDB issues. If ServiceNow determines your instance needs to be returned to MariaDB, engineering and support will work during the escalation to schedule emergency maintenance to return your instance to MariaDB, then work with your platform team to determine how best to retrieve data from RaptorDB. Note that this scenario requires additional downtime and may involve some data loss, depending on the issue.

Q: When can I schedule my RaptorDB Pro production migration?
A: Once your RaptorDB Pro entitlement is processing, work with your account team and the migration team to plan your subprod testing start dates and/or preferred production migration target cutover dates. Note that lead time is necessary to plan for hardware availability, setup, seeding, and cutover window scheduling.

Q: What if I don’t clone my sub prod instances right away to get them onto RaptorDB?
A: You may have a mix of MariaDB and RaptorDB instances within your account. Update sets continue to work as normal. Only clone from a RaptorDB source over a MariaDB or RaptorDB target. Do not clone a MariaDB source over a RaptorDB target.