Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Aplikasi standar menggunakan klien, seperti driver tingkat rendah atau pemetaan relasional objek (ORM) untuk
terhubung ke database. Spanner mendukung klien dalam beberapa bahasa
yang memungkinkan Anda menggunakan library umum, seperti JDBC, di seluruh lingkungan
developer. Untuk mengetahui informasi selengkapnya, lihat
Ringkasan driver.
Selain mengelola cara aplikasi terhubung ke Spanner,
Anda juga harus mengelola kueri yang dikirim dan sintaksis yang digunakan kueri.
Spanner mendukung dua dialek SQL, keduanya didasarkan pada standar ANSI SQL.
Anda dapat memilih untuk menggunakan antarmuka GoogleSQL atau PostgreSQL untuk Spanner berdasarkan
ekosistem tempat Anda ingin beroperasi. Untuk informasi selengkapnya, lihat
Memilih dialek yang tepat untuk database Spanner Anda.
Karena
perbedaan arsitektur antara database Spanner dan database
sumber Anda, sintaksis yang digunakan
di Spanner mungkin tidak sesuai dengan sintaksis database sumber Anda.
Selesaikan langkah-langkah berikut secara manual
untuk memigrasikan aplikasi Anda ke Spanner:
Spanner tidak mendukung kode pengguna yang berjalan di database, sehingga Anda perlu memindahkan prosedur dan pemicu yang disimpan di tingkat database ke aplikasi.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-11 UTC."],[],[],null,["# Migrate your application code\n\nA typical application uses a client, such as a low-level driver or an object-relational mapper (ORM) to\nconnect to the database. Spanner supports clients in multiple languages\nthat let you use common libraries, such as JDBC, across developer\nenvironments. For more information, see\n[Overview of drivers](/spanner/docs/drivers-overview).\n\nIn addition to managing how your application connects to Spanner,\nyou also have to manage which queries are sent and which syntax the queries are using.\nSpanner supports two SQL dialects, both based on ANSI SQL standard.\nYou can choose to use GoogleSQL or PostgreSQL interface for Spanner based\non the ecosystem you want to operate in. For more information, see\n[Choosing the right dialect for your Spanner database](/spanner/docs/choose-googlesql-or-postgres).\nBecause of the\narchitectural differences between the Spanner database and your\nsource database, the syntax used\nin Spanner might not align with the syntax of your source database.\n\nComplete the following steps manually\nto migrate your application to Spanner:\n\n- Spanner doesn't support running user code in the database,\n so you need to move any procedures and triggers stored at the database level\n into the application.\n\n- Use Spanner client libraries and ORMs. For more information, see\n [Overview of APIs, client libraries, and ORM drivers](/spanner/docs/api-libraries-overview).\n\n- Take note of [Spanner partitioned DML](/spanner/docs/dml-partitioned),\n [read-only transactions](/spanner/docs/transactions#read-only_transactions),\n [commit timestamps](/spanner/docs/commit-timestamp), and read timestamps and\n how they can optimize application performance.\n\n- You also might need to make changes to transaction handling. Consider the following:\n\n - The mutations per commit limit is 80,000. Each secondary index on a table is an additional mutation per row. To modify data using mutations, see [Insert, update, and delete data using mutations](/spanner/docs/modify-mutation-api). To modify a large amount of data, use [partitioned DML](/spanner/docs/dml-partitioned)."]]
