When you use Standard SQL to analyze large amounts of data, a single query may not scan all logs within a specific time range, which can result in incomplete data. Although adding shards improves read and write performance, this improvement applies only to new data. To analyze more data in a single query, enable Dedicated SQL and add more compute resources.
Operation description
Before you call this operation, make sure that you understand the billing methods and pricing for Dedicated SQL.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
log:UpdateSqlInstance |
update |
*Project
|
None | None |
Request syntax
PUT /sqlinstance HTTP/1.1
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| project |
string |
Yes |
The name of the project in which to enable Dedicated SQL. |
test-project |
| body |
object |
No |
The request struct. |
|
| cu |
integer |
Yes |
The number of Compute Units (CUs). A CU is a compute core that can be used for parallel processing when Dedicated SQL is running. |
2 |
| useAsDefault |
boolean |
Yes |
Specifies whether to enable Dedicated SQL for the project by default. If this parameter is set to true, all query and analysis operations in the project, such as alerts and dashboards, use Dedicated SQL. |
Response elements
|
Element |
Type |
Description |
Example |
None defined.
Examples
Success response
JSON format
{}
Error codes
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.