僅以內部 IP 位址 (無外部 IP 位址) 部署在 Compute Engine VM 執行個體上的第三方 BI 和資料分析解決方案可以使用 Private Google Access 來存取 Google API 和 BigQuery 之類的服務。您可以根據不同的子網路來決定是否啟用該子網路的私人 Google 存取權；這是虛擬私人雲端網路中的子網路設定。如要啟用子網路的私人 Google 存取權以及查看需求條件，請參閱設定私人 Google 存取權。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eThird-party BI and data analytics solutions can connect to BigQuery via the public BigQuery REST API and BigQuery Storage API over the internet, or through Private Google Access for internal or on-premises networks.\u003c/p\u003e\n"],["\u003cp\u003eFor solutions without direct BigQuery API integration, Magnitude Simba provides ODBC and JDBC drivers to facilitate connectivity.\u003c/p\u003e\n"],["\u003cp\u003eGoogle's BigQuery API uses OAuth 2.0 access tokens for authentication, which can be automatically generated by solutions with native integration, or obtained for user or service accounts via Simba drivers.\u003c/p\u003e\n"],["\u003cp\u003eWhen managing your own third-party BI solution instance, deploying it on Compute Engine can minimize latency between the solution and BigQuery.\u003c/p\u003e\n"],["\u003cp\u003eSetting filters in report or dashboard queries pushes WHERE clauses to BigQuery, reducing the amount of data transferred over the network even if the amount of scanned data remains the same.\u003c/p\u003e\n"]]],[],null,["# Integrate with third-party tools\n================================\n\nThis document describes initial configuration steps you might need to take to\nmanage the connection between BigQuery and your third-party\nbusiness intelligence (BI) solutions. If you need assistance with a solution,\nconsider contacting a [Google Cloud Ready - BigQuery\npartner](https://console.cloud.google.com/bigquery/partner-center). Third-party software is not\nsupported by Cloud Customer Care when it has been identified that\nBigQuery is working as intended.\n\n### Network connectivity\n\nAll BI and data analytics solutions that are deployed on hosts and services\nwith external IP addresses can access BigQuery through the public\n[BigQuery REST API](/bigquery/docs/reference/rest)\nand the RPC-based\n[BigQuery Storage API](/bigquery/docs/reference/storage)\nover the internet.\n\nThird-party BI and data analytics solutions that are deployed on\n[Compute Engine](/compute)\nVM instances only with internal IP addresses (no external IP addresses) can use\n[Private Google Access](/vpc/docs/private-google-access)\nto reach Google APIs and services like BigQuery. You enable\nPrivate Google Access on a subnet-by-subnet basis; it's a setting for subnets\nin a VPC network. To enable a subnet for Private Google Access and to view the\nrequirements, see\n[Configuring Private Google Access](/vpc/docs/configure-private-google-access).\n\nThird-party BI and data analytics solutions that are deployed on on-premises\nhosts can use\n[Private Google Access for on-premises hosts](/vpc/docs/private-google-access-hybrid)\nto reach Google APIs and services like BigQuery. This service\nestablishes a private connection over a\n[Cloud VPN](/network-connectivity/docs/vpn)\nor\n[Cloud Interconnect](/network-connectivity/docs/interconnect)\nfrom your data center to Google Cloud. On-premises hosts don't\nneed external IP addresses; instead, they use internal\n[RFC 1918](https://tools.ietf.org/html/rfc1918)\nIP addresses. To enable Private Google Access for on-premises hosts, you\nmust configure DNS, firewall rules, and routes in your on-premises and VPC\nnetworks. For more details on Private Google Access for on-premises\nhosts, see\n[Configuring Private Google Access for on-premises hosts](/vpc/docs/configure-private-google-access-hybrid).\n\nIf you opt to manage your own instance of a third-party BI solution, consider\ndeploying it on\n[Compute Engine](/compute)\nto take advantage of Google's network backbone and minimize latency between your\ninstance and BigQuery.\n\nIf your BI solution supports it, you might consider setting\nfilters in report or dashboard queries whenever possible.\nThis step pushes the filters as\n`WHERE` clauses to BigQuery. Although setting these filters\ndoesn't reduce the amount of data that BigQuery scans, it does\nreduce the amount of data that comes back over the network.\n\nFor more information on network and query optimizations, see\n[Migrating data warehouses to BigQuery: performance optimization](/architecture/dw2bq/dw-bq-performance-optimization)\nand the\n[Introduction to optimizing query performance](/bigquery/docs/best-practices-performance-overview).\n\n### API and ODBC/JDBC integrations\n\nGoogle's BI and data analytics products like\n[Looker Studio](/looker-studio),\n[Looker](/looker),\n[Dataproc](/dataproc),\nand\n[Vertex AI Workbench instances](/vertex-ai/docs/workbench/instances/introduction),\nand third-party solutions like\n[Tableau](https://www.tableau.com/),\noffer direct BigQuery integration using the\n[BigQuery API](/bigquery/docs/reference/libraries-overview).\n\nFor other third-party solutions and custom applications, Google has collaborated with\n[Magnitude Simba](https://www.magnitude.com/products/data-connectivity)\nto provide\n[ODBC](https://wikipedia.org/wiki/Open_Database_Connectivity)\nand\n[JDBC](https://wikipedia.org/wiki/Java_Database_Connectivity)\ndrivers.\nThe intent of these drivers is to help you leverage the power of\nBigQuery with existing tooling and infrastructure that doesn't\nintegrate with the [BigQuery API](/bigquery/docs/reference/libraries-overview).\n\nFor more details, see the Google Cloud documentation on\n[ODBC and JDBC Drivers for BigQuery](/bigquery/docs/reference/odbc-jdbc-drivers).\n\n### Authentication\n\nThe BigQuery API uses\n[OAuth 2.0](https://tools.ietf.org/html/rfc6749)\naccess tokens to authenticate requests. An OAuth 2.0 access token is a string\nthat grants temporary access to an API.\n[Google's OAuth 2.0 server](https://developers.google.com/identity/protocols/OAuth2WebServer#obtainingaccesstokens)\ngrants access tokens for all Google APIs. Access tokens are associated with a\n[scope](https://tools.ietf.org/html/rfc6749#section-3.3),\nwhich limits the token's access. For scopes associated with the\nBigQuery API, see the complete\n[list of Google API scopes](https://developers.google.com/identity/protocols/googlescopes#bigqueryv2).\n\nBI and data analytics solutions that offer native BigQuery\nintegration can automatically generate access tokens for BigQuery\neither by using\n[OAuth 2.0 protocols](https://developers.google.com/identity/protocols/OAuth2)\nor customer-supplied\n[service account private keys](/iam/docs/creating-managing-service-account-keys).\nSimilarly, solutions that rely on Simba ODBC/JDBC drivers can also obtain access\ntokens\n[for a Google user account](https://www.simba.com/products/BigQuery/doc/ODBC_InstallGuide/mac/content/odbc/bq/configuring/authenticating/useraccount.htm)\nor\n[for a Google service account](https://www.simba.com/products/BigQuery/doc/ODBC_InstallGuide/mac/content/odbc/bq/configuring/authenticating/serviceaccount.htm)."]]
