diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml
index acd63e70a663..0f274c232a0d 100644
--- a/.generator/schemas/v2/openapi.yaml
+++ b/.generator/schemas/v2/openapi.yaml
@@ -31063,9 +31063,17 @@ components:
           type: string
         values:
           description: |-
-            Column values in row order. The element type matches the column's `type`;
-            for example a `VARCHAR` column carries strings, a `TIMESTAMP` column carries
-            Unix-millisecond integers. `null` is allowed for missing values.
+            Column values in row order, one entry per result row. The element type
+            follows the column's `type`. The following serialization rules should be
+            taken into account:
+
+            - `BIGINT` values are encoded as JSON numbers in the signed 64-bit integer range.
+            - `DECIMAL` values are encoded as JSON numbers with 64-bit double precision.
+            - `TIMESTAMP` and `DATE` values are encoded as Unix-millisecond integers; a
+              `DATE` resolves to midnight UTC.
+            - `JSON` values are returned as a JSON-encoded string.
+
+            `null` is allowed for any column type where a value is missing.
           example:
             - web-store
             - checkout
@@ -135602,9 +135610,6 @@ paths:
       summary: Execute a tabular DDSQL query
       tags:
         - DDSQL
-      x-unstable: |-
-        **Note**: This endpoint is in preview and is subject to change.
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).
   /api/v2/ddsql/query/tabular/fetch:
     post:
       description: |-
@@ -135713,9 +135718,6 @@ paths:
       summary: Fetch the result of a DDSQL query
       tags:
         - DDSQL
-      x-unstable: |-
-        **Note**: This endpoint is in preview and is subject to change.
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).
   /api/v2/deletion/data/{product}:
     post:
       description: Creates a data deletion request by providing a query and a timeframe targeting the proper data.
diff --git a/lib/datadog_api_client/configuration.rb b/lib/datadog_api_client/configuration.rb
index 9d1245a1250d..f8efb320e7cf 100644
--- a/lib/datadog_api_client/configuration.rb
+++ b/lib/datadog_api_client/configuration.rb
@@ -432,8 +432,6 @@ def initialize
             "v2.get_all_datasets": false,
             "v2.get_dataset": false,
             "v2.update_dataset": false,
-            "v2.execute_ddsql_tabular_query": false,
-            "v2.fetch_ddsql_tabular_query": false,
             "v2.cancel_data_deletion_request": false,
             "v2.create_data_deletion_request": false,
             "v2.get_data_deletion_requests": false,
diff --git a/lib/datadog_api_client/v2/api/ddsql_api.rb b/lib/datadog_api_client/v2/api/ddsql_api.rb
index fbe77f4c1ddd..990ca327857d 100644
--- a/lib/datadog_api_client/v2/api/ddsql_api.rb
+++ b/lib/datadog_api_client/v2/api/ddsql_api.rb
@@ -41,12 +41,6 @@ def execute_ddsql_tabular_query(body, opts = {})
     # @param opts [Hash] the optional parameters
     # @return [Array<(DdsqlTabularQueryResponse, Integer, Hash)>] DdsqlTabularQueryResponse data, response status code and response headers
     def execute_ddsql_tabular_query_with_http_info(body, opts = {})
-      unstable_enabled = @api_client.config.unstable_operations["v2.execute_ddsql_tabular_query".to_sym]
-      if unstable_enabled
-        @api_client.config.logger.warn format("Using unstable operation '%s'", "v2.execute_ddsql_tabular_query")
-      else
-        raise DatadogAPIClient::APIError.new(message: format("Unstable operation '%s' is disabled", "v2.execute_ddsql_tabular_query"))
-      end
 
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: DDSQLAPI.execute_ddsql_tabular_query ...'
@@ -117,12 +111,6 @@ def fetch_ddsql_tabular_query(body, opts = {})
     # @param opts [Hash] the optional parameters
     # @return [Array<(DdsqlTabularQueryResponse, Integer, Hash)>] DdsqlTabularQueryResponse data, response status code and response headers
     def fetch_ddsql_tabular_query_with_http_info(body, opts = {})
-      unstable_enabled = @api_client.config.unstable_operations["v2.fetch_ddsql_tabular_query".to_sym]
-      if unstable_enabled
-        @api_client.config.logger.warn format("Using unstable operation '%s'", "v2.fetch_ddsql_tabular_query")
-      else
-        raise DatadogAPIClient::APIError.new(message: format("Unstable operation '%s' is disabled", "v2.fetch_ddsql_tabular_query"))
-      end
 
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: DDSQLAPI.fetch_ddsql_tabular_query ...'
diff --git a/lib/datadog_api_client/v2/models/ddsql_tabular_query_column.rb b/lib/datadog_api_client/v2/models/ddsql_tabular_query_column.rb
index 2fc6d124f076..d31aae87df29 100644
--- a/lib/datadog_api_client/v2/models/ddsql_tabular_query_column.rb
+++ b/lib/datadog_api_client/v2/models/ddsql_tabular_query_column.rb
@@ -31,9 +31,17 @@ class DdsqlTabularQueryColumn
     # for the full, up-to-date list.
     attr_reader :type
 
-    # Column values in row order. The element type matches the column's `type`;
-    # for example a `VARCHAR` column carries strings, a `TIMESTAMP` column carries
-    # Unix-millisecond integers. `null` is allowed for missing values.
+    # Column values in row order, one entry per result row. The element type
+    # follows the column's `type`. The following serialization rules should be
+    # taken into account:
+    #
+    # - `BIGINT` values are encoded as JSON numbers in the signed 64-bit integer range.
+    # - `DECIMAL` values are encoded as JSON numbers with 64-bit double precision.
+    # - `TIMESTAMP` and `DATE` values are encoded as Unix-millisecond integers; a
+    #   `DATE` resolves to midnight UTC.
+    # - `JSON` values are returned as a JSON-encoded string.
+    #
+    # `null` is allowed for any column type where a value is missing.
     attr_reader :values
 
     attr_accessor :additional_properties