Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Crittografia del traffico di rete
È una best practice criptare il traffico di rete tra l'applicazione Looker e il tuo database. Valuta una delle opzioni descritte nella pagina della documentazione Abilitare l'accesso sicuro ai database.
Utenti e sicurezza
Per eseguire azioni sul tuo database, Looker deve avere un account utente sul tuo database.
Per configurare un utente del database da utilizzare in Looker, segui questi passaggi nel database:
Concedi i privilegi SELECT all'utente del database sul database su cui vuoi che Looker esegua query. Sostituisci database_name con il nome del database.
Creazione della connessione Looker al tuo database
Per creare la connessione da Looker al tuo database:
Nella sezione Amministrazione di Looker, seleziona Connessioni e poi fai clic su Aggiungi connessione.
Dal menu a discesa Dialetto, seleziona Google Cloud SQL.
Compila i dettagli della connessione. La maggior parte delle impostazioni è comune alla maggioranza dei dialetti di database. Per informazioni, consulta la pagina della documentazione Connessione di Looker al tuo database. Di seguito sono descritte alcune impostazioni:
Host: il nome host del database utilizzato per connettersi al database Google Cloud SQL per MySQL. Per un tunnel SSH, utilizza localhost.
Porta: la porta utilizzata per connettersi al database Google Cloud SQL per MySQL.
Database: il nome dell'istanza di database Google Cloud SQL per MySQL.
Nome utente: il nome utente dell'account che Looker utilizzerà per accedere a Google Cloud SQL per MySQL.
Password: la password dell'account che Looker utilizzerà per accedere a Google Cloud SQL per MySQL.
SSL: se selezionata, attiva una connessione SSL; tuttavia, le connessioni SSL a Google Cloud SQL per MySQL non sono supportate per impostazione predefinita.
Verifica SSL: se selezionata, viene applicata la verifica SSL. Tuttavia, le connessioni SSL a Google Cloud non sono supportate per impostazione predefinita.
Per verificare che la connessione sia riuscita, fai clic su Testa. Per informazioni sulla risoluzione dei problemi, consulta la pagina della documentazione Testare la connettività del database.
Per salvare queste impostazioni, fai clic su Connetti.
Supporto PDT
Google Cloud SQL per MySQL non supporta le istruzioni CREATE TABLE AS SELECT, pertanto devi utilizzare il parametro LookML create_process per definire le PDT.
Funzionalità supportate
Affinché Looker supporti alcune funzionalità, anche il dialetto del database deve supportarle.
A partire da Looker 25.14, Google Cloud SQL supporta le seguenti funzionalità:
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-04 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)."]]
