If you use Standard SQL to analyze a large volume of data, a single query may not be able to scan all logs within a specified time range, which can result in incomplete data. Adding shards improves read and write performance, but this change applies only to new data. To analyze a larger volume of data in a single query, you can enable Dedicated SQL and increase its compute resources.
Operation description
Ensure that you understand the billing methods and pricing of Dedicated SQL before you use this operation.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
log:CreateSqlInstance |
create |
*Project
|
None | None |
Request syntax
POST /sqlinstance HTTP/1.1
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| project |
string |
Yes |
The name of the project for which you want to enable Dedicated SQL. |
test-project |
| body |
object |
No |
The request struct. |
|
| cu |
integer |
Yes |
The number of compute units (CUs). CUs are the compute cores that can be used in parallel when Dedicated SQL is running. |
2 |
| useAsDefault |
boolean |
Yes |
Specifies whether to enable Dedicated SQL by default for the project. If you set this parameter to `true`, all query and analysis operations in the project, such as alerting 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.