Documentation Grafana Cloud Connect to data sources Data sources Microsoft SQL Server Annotations

Microsoft SQL Server annotations

Annotations overlay event markers on your dashboard visualizations, helping you correlate metric behavior with events like deployments, incidents, or configuration changes. You can use the Microsoft SQL Server data source to create annotation queries that display SQL query results as annotation events.

For general information about annotations, refer to Annotate visualizations.

Before you begin

Before you create MSSQL annotations, ensure you have:

• A configured Microsoft SQL Server data source
• A table containing event data with at least a time column and a description column
• Familiarity with T-SQL query syntax

Create an annotation query

To add a Microsoft SQL Server annotation to your dashboard:

1. Navigate to your dashboard and click Dashboard settings (gear icon).
2. Select Annotations in the left menu.
3. Click Add annotation query.
4. Enter a Name for the annotation.
5. Select your Microsoft SQL Server data source from the Data source drop-down.
6. Write an SQL query that returns the required columns.
7. Click Save dashboard.

Annotation query columns

Your annotation query must return columns with specific names. Grafana uses these names to map query results to annotation fields.

Example: Annotation with epoch time

Given a table that stores events with Unix epoch timestamps:

SQL Copy

CREATE TABLE [events] (
  time_sec bigint,
  description nvarchar(100),
  tags nvarchar(100),
)

Query to display events as annotations:

SQL Copy

SELECT
  time_sec as time,
  description as [text],
  tags
FROM
  [events]
WHERE
  $__unixEpochFilter(time_sec)
ORDER BY 1

The $__unixEpochFilter macro automatically filters events to the dashboard’s selected time range.

Example: Region annotation with start and end times

To display annotations as shaded regions (spanning a duration), include both time and timeend columns:

SQL Copy

SELECT
  time_sec as time,
  time_end_sec as timeend,
  description as [text],
  tags
FROM
  [events]
WHERE
  $__unixEpochFilter(time_sec)
ORDER BY 1

Example: Annotation with native datetime column

If your table uses native SQL datetime or datetime2 columns instead of epoch values:

SQL Copy

SELECT
  time,
  measurement as text,
  convert(varchar, valueOne) + ',' + convert(varchar, valueTwo) as tags
FROM
  metric_values
WHERE
  $__timeFilter(time)
ORDER BY 1

The $__timeFilter macro works with native SQL date/time types and filters to the dashboard time range.

Example: Deployment annotations

Display deployment events on your graphs:

SQL Copy

SELECT
  deployed_at as time,
  'Deployed ' + version + ' to ' + environment as [text],
  environment as tags
FROM
  [deployments]
WHERE
  $__timeFilter(deployed_at)
ORDER BY 1

Example: Maintenance window annotations

Display maintenance windows as shaded regions:

SQL Copy

SELECT
  start_time as time,
  end_time as timeend,
  'Maintenance: ' + description as [text],
  'maintenance' as tags
FROM
  [maintenance_windows]
WHERE
  $__timeFilter(start_time)
ORDER BY 1

Use template variables

You can use template variables in your annotation queries to make them dynamic. For example, filter events by a selected server:

SQL Copy

SELECT
  time_sec as time,
  description as [text],
  tags
FROM
  [events]
WHERE
  $__unixEpochFilter(time_sec)
  AND server IN ($server)
ORDER BY 1

Macros

Use these macros in your annotation queries to filter by the dashboard time range:

For the full list of available macros, refer to the Microsoft SQL Server query editor.

Best practices

Follow these best practices when creating Microsoft SQL Server annotations:

• Use time filters: Always include $__timeFilter() or $__unixEpochFilter() to limit results to the dashboard time range.
• Keep queries efficient: Add indexes on time columns and filter columns to improve query performance.
• Use meaningful text: Include descriptive information in the text column to make annotations useful at a glance.
• Organize with tags: Use consistent tag values to categorize annotations and enable filtering.
• Test queries first: Verify your query returns expected results in Explore before adding it as an annotation.

Get help

If your annotations aren’t appearing or behaving as expected, refer to Troubleshoot Microsoft SQL Server data source issues for common solutions.