CREATE MODEL

Related topics

• BigQuery works with CREATE MODEL From the official documentation: “This document describes the `CREATE MODEL` statement for importing [TensorFlow Lite](https://ai.google.dev/edge/litert) models into BigQuery by using SQL.”
• CREATE MODEL depends on Cloud Storage From the official documentation: “The following steps show you how to import the sample ONNX model from Cloud Storage by using a [`CREATE MODEL`](/bigquery/docs/reference/standard-sql/bigqueryml-syntax-create-onnx) statement.”
• CREATE MODEL configures remote model From the official documentation: “Use the [`CREATE MODEL`](/bigquery/docs/reference/standard-sql/bigqueryml-syntax-create-remote-model) statement to create a remote model that represents a hosted Agent Platform model:”
• CREATE MODEL is part of Spanner From the official documentation: “To register this model in a Spanner database, [execute](/spanner/docs/schema-updates) the following DDL [statement](/spanner/docs/reference/standard-sql/data-definition-language#create_model): ```sql CREATE MODEL TextBison INPUT (prompt STRING(MAX)) OUTPUT (content STRING(MAX))…”
• BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
• BigQuery works with Cloud Storage From the official documentation: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Cloud SQL works with Cloud Storage From the official documentation: “Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.”
• Customer-Managed Encryption Keys secures Cloud Storage From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
• BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
• Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
• Dataflow works with Spanner From the official documentation: “Use Dataflow to load data into Spanner.”
• Customer-Managed Encryption Keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• BigQuery works with Spanner From the official documentation: “Federated analytics seamlessly combine data from Spanner and other sources in BigQuery.”
• BigQuery works with Gemini Enterprise Agent Platform From the official documentation: “The BigQuery dataset stores all versions for the associated Gemini Enterprise Agent Platform dataset.”
• Cloud Storage works with Customer-Managed Encryption Keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• Cloud Logging works with Cloud SQL From the official documentation: “Database Migration Service and Cloud SQL use Cloud Logging.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Customer-Managed Encryption Keys secures BigQuery From the official documentation: “You can either create CMEKs manually to protect your BigQuery resources or use Cloud KMS Autokey.”
• Cloud Logging works with Gemini Enterprise Agent Platform From the official documentation: “When you run a training job, Gemini Enterprise Agent Platform training saves logs to [Logging](/logging/docs).”
• Cloud resource connection works with Cloud Storage From the official documentation: “Cloud resource connection lets BigQuery access Cloud Storage object data and metadata using its own service account.”
• Cloud resource connection works with Gemini Enterprise Agent Platform From the official documentation: “BigQuery uses a [Cloud resource connection](/bigquery/docs/create-cloud-resource-connection) to interact with the Gemini Enterprise Agent Platform endpoint.”
• Cloud Storage works with Gemini Enterprise Agent Platform From the official documentation: “When you perform custom training, Agent Platform usually loads your data from Cloud Storage.”
• Customer-Managed Encryption Keys secures Gemini Enterprise Agent Platform From the official documentation: “Enable customer-managed encryption keys (CMEK) for the Gemini Enterprise Agent Platform to gain more control over data encryption and key management.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Cloud resource connection From the official documentation: “After you create the training dataset, you establish a connection to link BigQuery and external sources.”
• Cloud Logging is an alternative to Cloud Storage From the official documentation: “Instead, they are routed to either Cloud Storage (recommended) or Cloud Logging, depending on your organization's configuration.”
• Cloud Logging works with Customer-Managed Encryption Keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Cloud resource connection is part of BigQuery From the official documentation: “A Cloud resource connection in BigQuery lets you connect BigQuery to other Google Cloud services and external storage by using a dedicated service account with delegated access.”
• Cloud resource connection works with Spanner From the official documentation: “A Cloud resource connection associated with a service account is used to connect to the Spanner.”
• Cloud SQL is an alternative to Spanner From the official documentation: “If a workload requires transaction processing with strong relational consistencies, [Spanner](/spanner/docs/overview) or [Cloud SQL](/sql/docs) can be better alternatives.”
• Customer-Managed Encryption Keys depends on Cloud Storage From the official documentation: “If used for storing Customer-managed Encryption Keys (CMEK): Cloud Storage (See [Cloud Storage pricing](/storage/pricing).)”
• Dataflow depends on Cloud Storage From the official documentation: “Begin by creating a Cloud Storage bucket using the Google Cloud console or Google Cloud CLI. The Dataflow pipeline uses this bucket as a temporary storage location.”
• remote model depends on Gemini Enterprise Agent Platform From the official documentation: “Create a remote model that represents a hosted Agent Platform model:”
• BigQuery depends on Cloud resource connection From the official documentation: “BigQuery uses a [Cloud resource connection](/bigquery/docs/create-cloud-resource-connection) to interact with the Cloud AI service.”
• BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
• BigQuery works with remote model From the official documentation: “The function uses a BigQuery ML [remote model](/bigquery/docs/reference/standard-sql/bigqueryml-syntax-create-remote-model-service) to connect BigQuery to the Cloud Natural Language API.”
• Cloud Logging depends on Customer-Managed Encryption Keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Cloud Logging works with Dataflow From the official documentation: “You can control the volume of Dataflow logs ingested by Cloud Logging by following the [Filter logs documentation](/dataflow/docs/guides/filter-logs).”
• Cloud Logging works with Spanner From the official documentation: “Both Spanner and Agent Platform provide monitoring dashboards and write logs to Cloud Logging, which can contain additional details.”
• Cloud resource connection depends on Cloud Storage From the official documentation: “- `CONNECTION_ID`: A `STRING` value that contains a [Cloud resource connection](/bigquery/docs/create-cloud-resource-connection) that the service can use to access the objects in Cloud Storage, in the format `location.connection_id`.”
• Cloud resource connection works with remote model From the official documentation: “Create a [Cloud resource connection](/bigquery/docs/create-cloud-resource-connection) for the remote model to use, and get the connection's service account.”
• Cloud SQL depends on Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Cloud SQL works with Dataflow From the official documentation: “Use Datastream to replicate changes from your MySQL instance to either BigQuery or Cloud Storage, and then use Dataflow or Managed Service for Apache Spark to bring the data into your Cloud SQL instance.”
• Cloud Storage works with Spanner From the official documentation: “Move Spanner databases to and from Avro or CSV files stored in Cloud Storage.”
• Customer-Managed Encryption Keys is part of BigQuery From the official documentation: “If you require more control over encryption keys, BigQuery supports [customer-managed encryption keys](/bigquery/docs/customer-managed-encryption) in the [Cloud Key Management Service](/kms/docs).”
• Customer-Managed Encryption Keys configures Cloud Logging From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Customer-Managed Encryption Keys secures Cloud Logging From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Customer-Managed Encryption Keys is part of Cloud SQL From the official documentation: “Cloud SQL also lets you add another layer of encryption to data using [customer-managed encryption keys (CMEK)](/sql/docs/postgres/cmek).”
• Customer-Managed Encryption Keys is part of Cloud Storage From the official documentation: “[Cloud Storage](/storage/docs/introduction) provides features such as customer-managed encryption, lifecycle management, and aging and retention policies.”
• Customer-Managed Encryption Keys works with Dataflow From the official documentation: “This sample shows how to use encryption keys managed by the customer, with a Dataflow pipeline.”
• Customer-Managed Encryption Keys secures Dataflow From the official documentation: “You can either create CMEKs manually to protect your Dataflow resources or use Cloud KMS Autokey.”
• Customer-Managed Encryption Keys works with Spanner From the official documentation: “`SPANNER_PROJECT` - A Google Cloud project that contains a Spanner instance which uses the customer-managed encryption keys (CMEKs) that reside in `KEY_PROJECT`.”
• Customer-Managed Encryption Keys secures Spanner From the official documentation: “To learn how to use manually-created CMEKs to protect your Spanner resources, see [Secure a database with CMEK](/spanner/docs/use-cmek).”
• Gemini Enterprise Agent Platform depends on Cloud Storage From the official documentation: “Certain tasks in Agent Platform require that you use additional Google Cloud products besides Agent Platform. For example, in most cases, you must use Cloud Storage and Artifact Registry when you create a custom training pipeline.”
• Gemini Enterprise Agent Platform works with remote model From the official documentation: “Create a remote model that represents a hosted Agent Platform `gemini-3.5-flash-lite` model:”
• Gemini Enterprise Agent Platform works with Spanner From the official documentation: “MODEL DDL statements and ML functions in Spanner invoke Gemini Enterprise Agent Platform endpoints and can fail due to various reasons:”