About migrated to RaptorDB

Masayoshi Kishi
Tera Expert

Our internal ServiceNow Production instance has been migrated to RaptorDB.
The Non-Production environments remain on MariaDB.

We have observed several issues, and we have already requested improvements from ServiceNow.

With that in mind, I would like to ask how others have approached this situation.


1, Was the migration of Non-Production to RaptorDB performed by cloning from Production?
ServiceNow has informed us that, due to resource constraints, the migration of Non-Production environments must be carried out by the customer.

2, Issues have been identified with Database Views (unfortunately, I no longer have the KB article URL).
Could you please share any other issues you encountered?

3, When upgrading Non-Production to RaptorDB, what were the key points you checked during functional validation and testing?

1 ACCEPTED SOLUTION

Hello Masayoshi, 

The migration planning as far as I know is mainly for RaptorDB pro customers however for RaptorDB standard, its always the production that is migrated and sub production instances are then cloned. 

View solution in original post

5 REPLIES 5

Hello Masayoshi, 

The migration planning as far as I know is mainly for RaptorDB pro customers however for RaptorDB standard, its always the production that is migrated and sub production instances are then cloned.