About migrated to RaptorDB

[Masayoshi Kishi]

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?

[Brad Bowman]

This seems backwards, and was not at all our experience - maybe because we have impact / premium support / something that we're paying a lot of money for in addition to licensing, and we are using the typical cloud model, we're not hosting.  I didn't know that a customer could upgrade their own database version, and why on earth would anything be done in a production instance before it's done in sub-prods?  We have not experienced / found any issues during or after the migration.

[Mark Roethof]

Hi there,

For one of my customers recently also got RaptorDB (not pro), and... like you are mentioning directly production.

Subproduction is mentioned that that will happen when performing a System Clone. Although I haven't seen this happen with a System Clone last week (still need to open a case for that).

[Pavan Srivastav]

Hello Masayoshi,

- ServiceNow will migrate only the production instances to RaptorDB and then customers will have to immediately clone the sub production instances to get raptorDB on them. 

https://www.servicenow.com/community/servicenow-ai-platform-blog/servicenow-raptordb-migration-frequ...

Potential issues which can occur with database views which have been migrated to a RaptorDB-based instance and how to handle and correct them - https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1642144

[Masayoshi Kishi]

@Pavan Srivastav 
Thank you for your Replay.
For example, do you have any information on whether customers with an Impact Advanced contract have, after consulting with their Account Manager, migrated to RaptorDB starting with Non-Production environments in a phased manner?