Performance Optimized Database v2 (Kagami) - Haraka Customer FAQ General Notes: What is the Performance Optimized Database v2?Why should customers adopt the Performance Optimized Database v2? Can customer test sub-production instances before rolling out on production instances? What are the prerequisites for an instance to be Performance Optimized Database v2-ready? What is the Performance Optimized Database v2 onboarding process? Do any Performance Optimized Database v2 onboarding processes require instance downtime? What is the process to obtain customer approval to deploy Performance Optimized Database v2? Can customer reschedule one or all Performance Optimized Database v2 onboarding changes? What is the process for handling customer issues post-onboarding? Can customers rollback Performance Optimized Database v2 changes if they experience issues? What are the secondary database categories routed to Performance Optimized Database v2? What are the future plans for the Performance Optimized Database v2? #1. Q: What is Performance Optimized Database v2? A: Performance Optimized Database v2 is the next generation of the Performance Optimized Database. Performance Optimized Database is an additional Read-Replica database technology in use for optimizing large, complex analytic type queries for specific customers. V2 is more performant in larger variety of use cases than the original version. #2. Q: Why should customers adopt Performance Optimized Database v2? A: Complex queries associated with tables serviced by Performance Optimized Database v2 will see an aggregate performance improvement. Compared to the legacy Performance Optimized Database, customers should expect to see faster system performance in aggregate when running with Performance Optimized Database v2. Performance Optimized Database v2 also has better runtime stability, reliability, and better system resource utilization. All current Performance Optimized Database customers will be migrated to Performance Optimized Database v2 starting September 2022. #3. Q: Can a customer test sub-production instances before rolling out on production instances? A: Performance Optimized Database v2 is being deployed only on production instances. #4. Q: What are the prerequisites for an instance to be Performance Optimized Database v2-ready? A: The instance must be on one of the following releases before configuration can begin: Primary database configured to use row-based replication.San Diego SP5 or higher Tokyo – all releases or higher #5. Q: What is the Performance Optimized Database v2 onboarding process? A: This depends in the customer already has the original Performance Optimized Database. All customers will go through the first 2 stages of deployment. Existing Performance Optimized Database customers upgrading to v2 will need to go through 4 stages to complete the migration. This is a gradual process that takes around 3 weeks. During this time, the overall system performance should gradually improve until the process is complete. Stage 1: Deploy Performance Optimized Database v2 and start collecting query stats (1 week) This process takes about 1 week to collect eligible queries in the instance and evaluate their performance against MariaDB and the v1 (if already installed) and v2 Performance Optimized Database engines. Stage 2: Ensure Performance Optimized Database v2 performance exceeds v1 in aggregate (1 week) Once all Queries have been collected and evaluated in Stage 1, ServiceNow will evaluate queries in aggregate and tune Performance Optimized Database v2 if necessary to ensure overall positive performance gain. Stage 3: Deactivate Performance Optimized Database v1 (1 week, if applicable) In this stage, the original Performance Optimized Database will be still in place but inactive. No queries will be routed to it. This is to ensure there is no negative impact to the instance. During this stage ServiceNow will continue to monitor the instance and will perform query tuning if necessary. If any instance stability concern is raised, ServiceNow can quickly reactivate the v1 Performance Optimized Database. ServiceNow will ensure the issues are resolved before attempting to deactivate the v1 Performance Optimized Database again. Stage 4: Retire Performance Optimized Database v1 (if applicable) The legacy Performance Optimized Database v1 database is retired and removed from the instance to complete the Performance Optimized Database v2 on boarding process #6. Q: Do any Performance Optimized Database v2 onboarding process require instance downtime? A: No customer downtime is required to add Performance Optimized Database v2 to an existing instance. #7. Q: What is the process to obtain customer approval to deploy Performance Optimized Database v2? A: ServiceNow SAM team will contact each customer to work out on boarding schedule and logistics. #8. Q: Can customers reschedule one or all Performance Optimized Database v2 onboarding changes? A: Customers can contact ServiceNow Support Account Manager (SAM) team or the customer can open a customer support case ticket to reschedule. #9. Q: What is the process for handling customer issues post-onboarding? A: All customer issues related to Performance Optimized Database v2 should be handled via standard case handling and escalation processes. #10. Q: Can customers rollback Performance Optimized Database v2 changes if they experience issues? A: During the onboarding process, there will be a change open for customer and SN communication. However, if any issues arise, customers can reach out through customer support case on Now Support and ServiceNow will assess the best action to ensure instance performance and user experience. #11. Q: What are the secondary database categories routed to Performance Optimized Database v2? A: For existing Performance Optimized Database v1 customers, the initial set will be a direct copy of what is currently selected in their Performance Optimized Database today. For new customers, the tables will be determined by analyzing the usage of the customer's ServiceNow instance to determine the initial set of tables that will benefit from the Performance Optimized Database v2. Depending on the workload of each instance, additional tables may be added in the future if it can benefit from Performance Optimized Database v2. #12. Q: What are the future plans for the Performance Optimized Database v2? A: Performance Optimized Database v2 will continue to support replicating more tables to allow instances to leverage Performance Optimized Database v2 capabilities. We will also periodically introduce performance enhancements and bug fixes.