Skip to content
Lucas Lessa
Voltar para as notícias
DatabricksDescontinuadoImpacto: Alto

Retirement of DeepSeek V4 Pro (0813) model on Databricks

The DeepSeek V4 Pro (0813) model will be retired on October 30, 2026. Migrate your workloads to DeepSeek V4.1 Flash.

O que mudou

Use cases

Imagine that your applications rely on DeepSeek V4 Pro (0813) through Foundation Model APIs and you need to find who owns these endpoints to migrate them to the recommended replacement.

How to use

Run the following SQL query to identify workloads using the deprecated model and find their owners:

SELECT
   eu.requester,
   se.endpoint_name,
   se.entity_name,
   COUNT(*) AS request_count,
   SUM(eu.input_token_count) AS total_input_tokens,
   SUM(eu.output_token_count) AS total_output_tokens,
   MIN(eu.request_time) AS first_request,
   MAX(eu.request_time) AS last_request
 FROM system.serving.endpoint_usage eu
 JOIN system.serving.served_entities se
   ON eu.served_entity_id = se.served_entity_id
 WHERE LOWER(se.entity_name) LIKE '%deepseek-v4-pro%'
 GROUP BY eu.requester, se.endpoint_name, se.entity_name
 ORDER BY request_count DESC

What happens in this code:

  1. Joins the endpoint usage and served entities system tables.
  2. Filters by the name of the retired model.
  3. Groups by requester and endpoint to aggregate call volume and token consumption.

Limitations and requirements

The DeepSeek V4 Pro (0813) model will be fully retired on October 30, 2026. After this date, any workloads using the model will stop working.

Ver nota oficial do Databricks

DeepSeek V4 Pro (0813) is scheduled for retirement

Resumo e explicação gerados por IA a partir da release note oficial. Em caso de dúvida, a documentação oficial da plataforma prevalece.

Relacionadas