Answer-first summary for fast verification
Answer: Utilize interleaved tables to store parent and children records together
Interleaved tables in Cloud Spanner efficiently store related records, such as orders and their items, together, enabling simultaneous reads of parent and child data. Cloud Bigtable, being a NoSQL database, isn't suited for this scenario. Cloud SQL lacks the scalability for global operations. The concept of 'interleaved hashes' does not exist in Cloud Spanner. For more details, refer to [Cloud Spanner documentation](https://cloud.google.com/spanner/docs/schema-and-data-model) and [optimizing schema design](https://cloud.google.com/spanner/docs/whitepapers/optimizing-schema-design).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A global transportation company has migrated an Oracle database to Cloud Spanner with minimal changes but is facing performance issues with joins, specifically between an orders table and an order items table. What recommendation would you make to improve join performance?
A
Utilize interleaved tables to store parent and children records together
B
Switch to Cloud Bigtable for enhanced join performance
C
Implement interleaved hashes within Cloud Spanner
D
Migrate to Cloud SQL for superior join performance