The core issue is that Databricks SQL alerts do not support dynamic evaluation using query parameters. When an alert is configured for a query that contains parameters, the alert's scheduled executions will only use the default values defined for those parameters in the query editor. The user's intent to have a configurable date range for the alert is not supported, as the alert will not prompt for new values or use different values on each run. Therefore, from the user's perspective of wanting a dynamic alert, the feature "does not work" as expected, making the use of parameters incompatible with this goal.

A. Alerts don't work with queries that access tables. This is incorrect. The primary function of alerts is to monitor data within tables.

B. Queries that return results based on dates cannot be used with Alerts. This is incorrect. Monitoring data based on dates (e.g., "today's sales") is a very common use case for alerts.

C. The wrong query parameter is being used. Alerts only work with Date and Time query parameters. This is incorrect. The limitation applies to all parameter types, not just Date.

E. The wrong query parameter is being used. Alerts only work with dropdown list query parameters, not dates. This is incorrect. The limitation is general to all query parameters, not specific to dates or dropdowns.

1. Databricks Documentation

"What are Databricks SQL alerts?": This document explicitly states the behavior of alerts with parameterized queries.

Reference: Under the section "Create an alert"

the documentation notes: "If the target query has parameters

the alert is evaluated using the default parameter values. To monitor the alert for specific parameter values

you must set them as the default in the target query." This confirms that parameters are not dynamic in the context of alerts.

Source: Databricks Official Documentation > Databricks SQL > What are Databricks SQL alerts?