[sqlserver] Add SQL Server 2025 to supported versions

[pierreln-dd]

What does this PR do? What is the motivation?

Adds SQL Server 2025 to the supported versions list in the SQL Server integration README.

SQL Server 2025 support confirmed in Agent 7.79+ via integrations-core#22794. DBM-specific docs updated separately in DataDog/documentation#36110.

Additional Information

Documentation-only change.

🤖 Generated with Claude Code

[dd-octo-sts]

Validation Report

All 20 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and Codecov settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run

[na-ji]

Do we really need to update changelog for a readme update?

[pierreln-dd]

Probably not for most README updates, but I think a major support version could still make sense?

[na-ji]

Oh right, I thought #22794 already added the changelog entry for that.

[cit-pr-commenter-54b7da]

Monitor Template Quality Assessment

52 monitors analyzed across 9 integrations.

• 31 monitors have missing sections
• Most common missing sections: WHY, IMPACT, HOW_TO_TROUBLESHOOT

Monitors with missing sections

Integration	Monitor	Missing Sections	Suggested Links
kubernetes	[Kubernetes] Monitor Kubernetes Deployments Replica Pods	IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS	- Logs

• Infrastructure
• Metrics Explorer (kubernetes_state.deployment.replicas_desired)
• Metrics Explorer (kubernetes_state.deployment.replicas_available) |
  | kubernetes | [Kubernetes] Monitor Unschedulable Kubernetes Nodes | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes_state.node.status) |
  | kubernetes | [Kubernetes] Pod {{pod_name.name}} is CrashloopBackOff on namespace {{kube_namespace.name}} | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes_state.container.status_report.count.waiting) |
  | kubernetes | [Kubernetes] Pod {{pod_name.name}} is ImagePullBackOff on namespace {{kube_namespace.name}} | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes_state.container.status_report.count.waiting) |
  | kubernetes | [Kubernetes] Pod {{pod_name.name}} is OOMKilled on namespace {{kube_namespace.name}} | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes.containers.state.terminated) |
  | kubernetes | [Kubernetes] Monitor Kubernetes Failed Pods in Namespaces | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes_state.pod.status_phase) |
  | kubernetes | [Kubernetes] Monitor Kubernetes Pods Restarting | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes.containers.restarts) |
  | kubernetes | [Kubernetes] Monitor Kubernetes Statefulset Replicas | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (kubernetes_state.statefulset.replicas_desired)
• Metrics Explorer (kubernetes_state.statefulset.replicas_ready) |
  | nginx | [NGINX] Upstream peers fails | WHY | - Logs
• Infrastructure
• Metrics Explorer (nginx.stream.upstream.peers.fails) |
  | postgres | [Postgres] Number of connections is approaching connection limit on {{host.name}} | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Metrics Explorer (postgresql.percent_usage_connections) |
  | postgres | [Postgres] Replication delay is abnormally high on {{host.name}} | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Metrics Explorer (postgresql.replication_delay) |
  | redis | [Redis] High memory consumption | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Metrics Explorer (redis.mem.used)
• Metrics Explorer (redis.mem.maxmemory) |
  | amazon-rds | [AWS] RDS CPU utilization is high | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (aws.rds.cpuutilization) |
  | amazon-rds | [AWS] RDS Anomaly in database connections | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (aws.rds.database_connections) |
  | amazon-rds | [AWS] RDS Storage utilization is high | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | - Logs
• Infrastructure
• Metrics Explorer (aws.rds.free_storage_space)
• Metrics Explorer (aws.rds.total_storage_space) |
  | apm | Abnormal change in p75 latency for $service.value on $env | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | Watchdog Anomaly: {{event.title}} for {{service}} | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | Monitor type is not supported for message generation: event-v2 alert |
  | apm | New issues found for $service on $env | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | High p95 latency for $service on $env | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | Abnormal change in Apdex for $service.value on $env | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | Low traffic on $service on $env | IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | New issues found for {{service}} on {{env}} | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | Monitor type is not supported for message generation: error-tracking alert |
  | apm | No data for $service.value on $env | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | apm | Increased error rate for $service.value in $env | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | no metrics found in query |
  | real-user-monitoring | View Error Rate is high for view {{[view.name].name}} | WHY | Unhandled exception while parsing message: parsing metric query failed: Rule 'or_op' didn't match at '.name} by {view.name' (line 1, column 53). |
  | real-user-monitoring | Interaction to Next Paint is high for view {{[view.name].name}} | WHY | Unhandled exception while parsing message: parsing metric query failed: Rule 'or_op' didn't match at '.name} by {view.name' (line 1, column 49). |
  | real-user-monitoring | App Startup Time is high | WHY | Unhandled exception while parsing message: parsing metric query failed: Rule 'or_op' didn't match at '.name}' (line 1, column 35). |
  | real-user-monitoring | Crash-Free Session Rate is low | WHY | Unhandled exception while parsing message: parsing metric query failed: Rule 'or_op' didn't match at '.name}.as_count() / ' (line 1, column 38). |
  | real-user-monitoring | Hang Rate is high | WHY | Unhandled exception while parsing message: parsing metric query failed: Rule 'or_op' didn't match at '.name}.as_count(), 2' (line 1, column 50). |
  | system | System load is high for host {{host.name}} | WHY | - Logs
• Infrastructure
• Metrics Explorer (system.load.norm.1) |
  | system | Host $host.value not reporting data | WHATS_HAPPENING, IMPACT, WHY, HOW_TO_TROUBLESHOOT, RELATED_LINKS | Monitor type is not supported for message generation: service check |