Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Mengenkripsi traffic jaringan
Praktik terbaiknya adalah mengenkripsi traffic jaringan antara aplikasi Looker dan database Anda. Pertimbangkan salah satu opsi yang dijelaskan di halaman dokumentasi Mengaktifkan akses database yang aman.
Pengguna dan keamanan
Untuk melakukan tindakan pada database Anda, Looker harus memiliki akun pengguna di database Anda.
Untuk mengonfigurasi pengguna database yang akan digunakan Looker, lakukan langkah-langkah berikut di database Anda:
Untuk membuat koneksi dari Looker ke database Anda, ikuti langkah-langkah berikut:
Di bagian Admin Looker, pilih Connections, lalu klik Add Connection.
Dari menu drop-down Dialek, pilih Google Cloud SQL.
Isi detail koneksi. Sebagian besar setelan umum untuk sebagian besar dialek database. Lihat halaman dokumentasi Menghubungkan Looker ke database Anda untuk mengetahui informasi selengkapnya. Beberapa setelan dijelaskan di bawah:
Host: Nama host database yang digunakan untuk terhubung ke database Google Cloud SQL untuk MySQL. Untuk tunnel SSH, gunakan localhost.
Port: Port yang digunakan untuk terhubung ke database Google Cloud SQL untuk MySQL.
Database: Nama instance database Google Cloud SQL untuk MySQL.
Nama pengguna: Nama pengguna akun yang akan digunakan Looker untuk login ke Google Cloud SQL untuk MySQL.
Sandi: Sandi akun yang akan digunakan Looker untuk login ke Google Cloud SQL untuk MySQL.
Parameter JDBC tambahan: Parameter JDBC tambahan (opsional).
SSL: Jika dicentang, mengaktifkan koneksi SSL; namun, koneksi SSL ke Google Cloud SQL untuk MySQL tidak didukung secara default.
Verifikasi SSL: Jika dicentang, verifikasi SSL akan diterapkan. Namun, koneksi SSL ke Google Cloud tidak didukung secara default.
Untuk memverifikasi bahwa koneksi berhasil, klik Uji. Lihat halaman dokumentasi Menguji konektivitas database untuk mengetahui informasi pemecahan masalah.
Untuk menyimpan setelan ini, klik Hubungkan.
Dukungan PDT
Google Cloud SQL untuk MySQL tidak mendukung pernyataan CREATE TABLE AS SELECT, jadi Anda harus menggunakan parameter LookML create_process untuk menentukan PDT.
Dukungan fitur
Agar Looker mendukung beberapa fitur, dialek database Anda juga harus mendukungnya.
Google Cloud SQL mendukung fitur berikut mulai Looker 25.12:
[[["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-25 UTC."],[],[],null,["# Google Cloud SQL for MySQL\n\n| **Note:** [Looker (Google Cloud core)](/looker/docs/looker-core-overview) instances support [Application Default Credentials (ADC)](/docs/authentication/application-default-credentials) as a method of authentication for Google Cloud SQL for MySQL. See the [Looker (Google Cloud core) documentation](/looker/docs/looker-core-dialects#using-application-default-credentials-to-connect-to-a-database) for more information.\n\nEncrypting network traffic\n--------------------------\n\nIt is a best practice to encrypt network traffic between the Looker application and your database. Consider one of the options described on the [Enabling secure database access](/looker/docs/enabling-secure-db-access) documentation page.\n\nUsers and security\n------------------\n\nTo perform actions on your database, Looker needs to have a user account on your database.\n| **Note:** Skip this procedure if you are on a Looker (Google Cloud core) instance and you want to use Application Default Credentials to authenticate into your database. You will instead use an existing IAM principal account. See the [Connecting Looker (Google Cloud core) to your database](/looker/docs/looker-core-dialects#using-application-default-credentials-to-connect-to-a-database) documentation page for the procedure.\n\nTo configure a database user for Looker to use, perform the following steps on your database:\n\n1. Create a database user.\n\n CREATE USER \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eUSERNAME\u003c/span\u003e\u003c/var\u003e;\n SET PASSWORD FOR \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eUSERNAME\u003c/span\u003e\u003c/var\u003e = PASSWORD ('\u003cvar translate=\"no\"\u003ePASSWORD\u003c/var\u003e');\n\n2. Grant `SELECT` privileges to the database user on the database that you want Looker to query. Replace `database_name` with the name of your database.\n\n GRANT SELECT ON \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eDATABASE_NAME\u003c/span\u003e\u003c/var\u003e.* TO \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eUSERNAME\u003c/span\u003e\u003c/var\u003e;\n\nOnce you create the database user, you can enter the database user account credentials in the [**Username**](#username) and [**Password**](#password) fields of the Looker UI when you [create the Looker connection to your database](#creating-the-connection-to-your-database).\n\nCreating the Looker connection to your database\n-----------------------------------------------\n\nTo create the connection from Looker to your database, follow these steps:\n\n1. In the **Admin** section of Looker, select **Connections** , and then click **Add Connection**.\n2. From the **Dialect** drop-down menu, select **Google Cloud SQL**.\n3. Fill out the connection details. The majority of the settings are common to most database dialects. See the [Connecting Looker to your database](/looker/docs/connecting-to-your-db) documentation page for information. Some of the settings are described next:\n\n - **Host** : The database hostname that is used to connect to the Google Cloud SQL for MySQL database. For an SSH tunnel, use `localhost`.\n - **Port**: The port used that is to connect to the Google Cloud SQL for MySQL database.\n - **Database**: The name of the Google Cloud SQL for MySQL database instance.\n - **Username** : The username of the account that Looker will use to sign in to Google Cloud SQL for MySQL.\n\n | **Note:** [Looker (Google Cloud core)](/looker/docs/looker-core-overview) instances also support [Application Default Credentials (ADC)](/docs/authentication/application-default-credentials) as a method of authentication for Google Cloud SQL for MySQL. See the [Looker (Google Cloud core) documentation](/looker/docs/looker-core-dialects#using-application-default-credentials-to-connect-to-a-database) for more information.\n - **Password** : The password of the account that Looker will use to sign in to Google Cloud SQL for MySQL.\n\n - **Additional JDBC parameters**: Additional JDBC parameters (optional).\n\n - **SSL**: If checked, enables an SSL connection; however, SSL connections to Google Cloud SQL for MySQL are not supported by default.\n\n | **Note:** Google Cloud SQL for MySQL requires additional steps for configuring SSL connections; see [Configuring SSL/TLS certificates](/sql/docs/mysql/configure-ssl-instance). Google Cloud SQL for MySQL creates a server certificate on the creation of each instance, so the custom certificate must be installed on the Looker server for successful SSL connections. This option is available only for [customer-hosted Looker deployments](/looker/docs/customer-hosted-installation-steps) that have access to the Looker server.\n |\n | \u003cbr /\u003e\n |\n | \u003cbr /\u003e\n |\n | Because of this requirement, a better alternative to SSL is to connect Looker to Google Cloud SQL for MySQL through a [Cloud SQL for MySQL Proxy](/sql/docs/mysql/sql-proxy).\n - **Verify SSL**: If checked, SSL verification is enforced. However, SSL connections to Google Cloud are not supported by default.\n\n4. To verify that the connection is successful, click **Test** . See the [Testing database connectivity](/looker/docs/testing-db-connectivity) documentation page for troubleshooting information.\n\n5. To save these settings, click **Connect**.\n\nPDT support\n-----------\n\nGoogle Cloud SQL for MySQL does not support `CREATE TABLE AS SELECT` statements, so you must use the [`create_process`](/looker/docs/reference/param-view-create-process) LookML parameter to define PDTs.\n\nFeature support\n---------------\n\nFor Looker to support some features, your database dialect must also support them.\n\nGoogle Cloud SQL supports the following features as of Looker 25.14:\n\nNext steps\n----------\n\nAfter you have created your database connection, [set authentication options](/looker/docs/getting-started-with-users)."]]
