If you use the Standard SQL feature to analyze a large amount of data, the logs within the specified time range cannot be fully scanned in a single query request. In this case, the returned results may not contain all matched data. You can increase the number of shards to improve data read and write capabilities. However, this method takes effect only for incremental data. You can enable the Dedicated SQL feature to increase computing resources and the amount of data that can be analyzed in a single query request.
Operation description
**Before you call this operation, make sure that you fully understand the billing of Dedicated SQL.
Debugging
Authorization information
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 the Dedicated SQL feature. | |
body | object | No | The request struct. | |
cu | integer | Yes | The number of compute units (CUs). When you use the Dedicated SQL feature, CUs are used in parallel. | 2 |
useAsDefault | boolean | Yes | Specifies whether to enable the Dedicated SQL feature for the project. If you set this parameter to true, the Dedicated SQL feature is enabled for the specified project and takes effect for all query statements that you execute in the project, including the query statements for alerts and dashboards. |
Response parameters
Examples
Sample success responses
JSON
format
{}
Error codes
For a list of error codes, visit the Service error codes.