Spanner Data Boost 是全代管的無伺服器服務，可為支援的 Spanner 工作負載提供獨立運算資源。您可以使用 Data Boost 執行分析查詢和資料匯出作業，對已佈建 Spanner 執行個體的現有工作負載幾乎不會造成任何影響。這項服務包含 Google 在區域層級管理的 Spanner 叢集。對於要求 Data Boost 的符合資格查詢，Spanner 會以透明化的方式將工作負載導向這些伺服器。符合資格的查詢是指查詢執行計劃中第一個運算子為分散式聯集的查詢。您不必變更這些查詢，即可充分運用 Data Boost。
[[["容易理解","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-05 (世界標準時間)。"],[],[],null,["# Data Boost overview\n\nSpanner Data Boost is a fully managed, serverless service that provides\nindependent compute resources for supported Spanner workloads.\nData Boost lets you execute analytics queries and data exports\nwith near-zero impact to existing workloads on the provisioned\nSpanner instance. The service consists of Spanner\nclusters that Google manages at the region level. For eligible queries that\nrequest Data Boost, Spanner routes the workload to\nthese servers transparently. Eligible queries are those for which the first\noperator in the query execution plan is a distributed union. These queries don't\nhave to change to take advantage of Data Boost.\n\nData Boost is most impactful in the following scenarios where you\nwant to avoid negative impacts to the existing transactional system due to\nresource contention:\n\n- Ad hoc or infrequent queries that involve processing large amounts of data. A typical example is a [federated\n query](/bigquery/docs/spanner-federated-queries) from BigQuery to Spanner.\n- Reporting or data export jobs. An example is a Dataflow job to export Spanner data to Cloud Storage.\n\nThe following diagram illustrates how Data Boost coordinates with\nthe Spanner instance to provide independent compute resources.\n\nBenefits\n--------\n\nData Boost offers the following benefits:\n\n- Provides workload isolation. You can run supported queries against the latest data with near-zero impact on existing transactional workloads regardless of query complexity or amount of data processed.\n- Provides equal or better latency.\n- Prevents over-provisioning of Spanner instances just to support occasional analytics queries.\n- Offers a high degree of scalability with greater query parallelism that scales elastically with burst loads.\n- Provides comprehensive metrics, which let administrators identify the most expensive queries and determine the cost component to optimize. Administrators can then verify the impact of their optimizations by monitoring the query's serverless processing unit consumption in its next execution.\n- Requires no additional operational overhead. There is no extra service to manage, no capacity planning or provisioning, no need to wait for scaling, and no maintenance.\n\nPermissions\n-----------\n\nAny principal that runs a query or export that requests Data Boost\nmust have the `spanner.databases.useDataBoost` Identity and Access Management (IAM)\npermission. We recommend that you use the\n`Cloud Spanner Database Reader With DataBoost` (`roles/spanner.databaseReaderWithDataBoost`)\nIAM role.\n\nBilling and quotas\n------------------\n\nYou pay only for actual processing units used by queries that run on\nData Boost. Administrators can set limits on usage to avoid cost\noverruns.\n\nWhat's next\n-----------\n\n- [Run federated queries with Data Boost](/spanner/docs/databoost/databoost-run-queries)\n- [Export data with Data Boost](/spanner/docs/databoost/databoost-export)\n- [Use Data Boost in your applications](/spanner/docs/databoost/databoost-applications)\n- [Monitor Data Boost usage](/spanner/docs/databoost/databoost-monitor)\n- [Monitor and manage Data Boost quota usage](/spanner/docs/databoost/databoost-quotas)"]]
