From 20db6b3c5dd25a75e1c086f4e1a58819669c0074 Mon Sep 17 00:00:00 2001
From: Colton Padden <colton@dagsterlabs.com>
Date: Wed, 18 Dec 2024 16:51:35 -0500
Subject: [PATCH] [docs] remove note that concurrency is only supported for
 non-sqlite databases

---
 .../guides/limiting-concurrency-in-data-pipelines.mdx        | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/docs/content/guides/limiting-concurrency-in-data-pipelines.mdx b/docs/content/guides/limiting-concurrency-in-data-pipelines.mdx
index 010eb5a11e278..ab45e8b7e61e1 100644
--- a/docs/content/guides/limiting-concurrency-in-data-pipelines.mdx
+++ b/docs/content/guides/limiting-concurrency-in-data-pipelines.mdx
@@ -391,11 +391,6 @@ height={1638}
 
 ### Limiting op/asset concurrency across runs
 
-<Note>
-  This feature is experimental and is only supported with Postgres/MySQL
-  storages.
-</Note>
-
 #### For specific ops/assets
 
 Limits can be specified on the Dagster instance using the special op tag `dagster/concurrency_key`. If this instance limit would be exceeded by launching an op/asset, then the op/asset will be queued.