How-to

Migrating From Oracle OLTP System to Cloud Spanner

765

Of your peers have already read this article.

8:30 Minutes

The most insightful time you'll spend today!

Find out how to migrate your database from Oracle Online Transaction Processing (OLTP) systems to Cloud Spanner.

Spanner uses certain concepts differently from other enterprise database management tools, so you might need to adjust your application to take full advantage of its capabilities. You might also need to supplement Spanner with other services from Google Cloud to meet your needs.

Migration constraints

When you migrate your application to Spanner, you must take into account the different features available. You probably need to redesign your application architecture to fit with Spanner’s feature set and to integrate with additional Google Cloud services.

Stored procedures and triggers

Spanner does not support running user code in the database level, so as part of the migration, you must move business logic implemented by database-level stored procedures and triggers into the application.

Sequences

Spanner does not implement a sequence generator, and as explained below, using monotonically increasing numbers as primary keys is an anti-pattern in Spanner. An alternative way to generate a unique primary key is to use a random UUID.

If sequences are required for external reasons, then you must implement them in the application layer.

Access controls

Spanner supports only database-level access controls using IAM access permissions and roles. Predefined roles can give read-write or read-only access to the database.

If you require finer grained permissions, you must implement them at the application layer. In a normal scenario, only the application should be allowed to read and write to the database.

If you need to expose your database to users for reporting, and want to use fine-grained security permissions (such as table- and view-level permissions), you should export your database to BigQuery.

Read the full article for more, including

  • Data validation constraints
  • Supported data types
  • Migration process
  • Transferring your data from Oracle to Spanner
  • Maintaining consistency between both databases
  • Verifying data consistency
  • and more.

More Relevant Stories for Your Company

Case Study

Case Study: When Database Choice Powers New Revenue-driving Product Features

Editor’s note: Streak makes a CRM add-on for Gmail, and recently adopted Cloud Spanner to take advantage of its scalability and SQL capabilities to implement a graph data model. Read on to learn about their decision, what they love about the system, and the ways in which it still needs

Case Study

How One Company Uses AI and Data Analysis to Boost Revenue

This improves the customer experience and enables retailers with online and offline outlets to provide a genuine omnichannel experience. The lack of complexity and the ease of use of BigQuery has enabled ViSenze to reduce its data infrastructure and management costs by 30%–50%, and scale up without incurring downtime. —Renjie

Case Study

BURGER KING Germany: Serving Up Marketing Insights and Supply Chain Visibility Easily

Do hamburgers really come from Hamburg? This may still be a matter of debate, but the popularity of American-style burger joints not just in Hamburg but all over Germany, is clear. Germany’s top two fast food companies are both burger chains. One of them is BURGER KING®, a global brand that welcomes more

Explainer

What is Cloud Spanner and Is It the Right Database for You?

You’ve probably heard about Cloud Spanner, but what exactly does it do that is so different from other databases out there? How do you know if it’s worth spending your valuable time trying out? Cloud Spanner is the first enterprise-grade, globally distributed, and strongly consistent database service built for the

SHOW MORE STORIES