diff --git a/apps/docs/content/troubleshooting/high-cpu-and-slow-queries-with-error-must-be-a-superuser-to-terminate-superuser-process.mdx b/apps/docs/content/troubleshooting/high-cpu-and-slow-queries-with-error-must-be-a-superuser-to-terminate-superuser-process.mdx
index d582f253bd0..7b1203a22e2 100644
--- a/apps/docs/content/troubleshooting/high-cpu-and-slow-queries-with-error-must-be-a-superuser-to-terminate-superuser-process.mdx
+++ b/apps/docs/content/troubleshooting/high-cpu-and-slow-queries-with-error-must-be-a-superuser-to-terminate-superuser-process.mdx
@@ -2,6 +2,7 @@
 title = "High CPU and Slow Queries with `ERROR: must be a superuser to terminate superuser process`"
 topics = [ "cli", "database", "storage" ]
 keywords = []
+database_id = "23668386-7a72-44ff-a412-4cd8a005fa18"
 ---
 
 When facing high CPU utilization, slow query performance, and an `ERROR: must be a superuser to terminate superuser process` message regarding an autovacuum, it indicates that a critical, non-terminable autovacuum operation is running on your Postgres database. This guide explains why this happens and what steps you can take.
diff --git a/apps/docs/content/troubleshooting/pgrst106-the-schema-must-be-one-of-the-following-error-when-querying-an-exposed-schema.mdx b/apps/docs/content/troubleshooting/pgrst106-the-schema-must-be-one-of-the-following-error-when-querying-an-exposed-schema.mdx
index 9ce9f234b81..0ade180ef7e 100644
--- a/apps/docs/content/troubleshooting/pgrst106-the-schema-must-be-one-of-the-following-error-when-querying-an-exposed-schema.mdx
+++ b/apps/docs/content/troubleshooting/pgrst106-the-schema-must-be-one-of-the-following-error-when-querying-an-exposed-schema.mdx
@@ -2,10 +2,11 @@
 title = "PGRST106: \"The schema must be one of the following...\" error when querying an exposed schema"
 topics = [ "auth", "database" ]
 keywords = []
+database_id = "91dda1aa-52f7-4a1c-9248-92fad9f3dec7"
+
 [[errors]]
 code = "PGRST106"
 message = "The schema must be one of the following: public, ..."
-
 ---
 
 You may encounter a `PGRST106` error, stating `{"code":"PGRST106","message":"The schema must be one of the following: public"}`, when attempting to query a schema via the PostgREST API that you've recently exposed.
diff --git a/apps/docs/content/troubleshooting/realtime-connections-timed_out-status.mdx b/apps/docs/content/troubleshooting/realtime-connections-timed_out-status.mdx
index 85b3f80c56c..c9dedebccd0 100644
--- a/apps/docs/content/troubleshooting/realtime-connections-timed_out-status.mdx
+++ b/apps/docs/content/troubleshooting/realtime-connections-timed_out-status.mdx
@@ -2,6 +2,7 @@
 title = "Realtime connections giving `TIMED_OUT` errors"
 topics = [ "realtime" ]
 keywords = []
+database_id = "b99fac0e-09da-4a31-93a1-6375ed8ce041"
 ---
 
 If your Realtime connections in your application are giving `TIMED_OUT` errors, this often indicates an incompatibility between the version of `realtime-js` being used in your `supabase-js` client library package and your Node.js version. This issue happens when using versions of Node.js older than v22 with more recent versions of `supabase-js`.
diff --git a/apps/docs/content/troubleshooting/sso-error-you-do-not-have-permissions-to-join-this-organization-or-prompts-to-create-new-organization.mdx b/apps/docs/content/troubleshooting/sso-error-you-do-not-have-permissions-to-join-this-organization-or-prompts-to-create-new-organization.mdx
index 4ec762f4942..e05c305a7a7 100644
--- a/apps/docs/content/troubleshooting/sso-error-you-do-not-have-permissions-to-join-this-organization-or-prompts-to-create-new-organization.mdx
+++ b/apps/docs/content/troubleshooting/sso-error-you-do-not-have-permissions-to-join-this-organization-or-prompts-to-create-new-organization.mdx
@@ -2,6 +2,7 @@
 title = "SSO Error: \"You do not have permissions to join this organization\" or prompts to create new organization"
 topics = [ "platform" ]
 keywords = []
+database_id = "37d147df-caa7-4b0b-82b5-eab6852f2cff"
 ---
 
 When attempting to log in via SSO, you may observe the message "You do not have permissions to join this organization" or be prompted to create a new organization.
diff --git a/apps/docs/content/troubleshooting/supabase-cli-failed-sasl-auth-or-invalid-scram-server-final-message.mdx b/apps/docs/content/troubleshooting/supabase-cli-failed-sasl-auth-or-invalid-scram-server-final-message.mdx
index 03a5bf2df61..2300d69883d 100644
--- a/apps/docs/content/troubleshooting/supabase-cli-failed-sasl-auth-or-invalid-scram-server-final-message.mdx
+++ b/apps/docs/content/troubleshooting/supabase-cli-failed-sasl-auth-or-invalid-scram-server-final-message.mdx
@@ -2,6 +2,7 @@
 title = "Supabase CLI: \"failed SASL auth\" or \"invalid SCRAM server-final-message\""
 topics = [ "auth", "cli", "database", "supavisor" ]
 keywords = []
+database_id = "4a32736f-1d7f-4c41-9c96-ab84e35ad394"
 ---
 
 When executing `supabase db push` or `supabase link` or any other authenticated actions from the Supabase CLI, you might encounter an authentication error with messages such as `failed SASL auth (invalid SCRAM server-final-message received from server)`.