Merging changes synced from https://github.com/MicrosoftDocs/sql-docs-pr (branch live)

Author: Learn Build Service GitHub App

azure-sql/database/monitoring-metrics-alerts.md

@@ -83,7 +83,6 @@ Here's the logic used for calculating Availability for every one-minute interval
 - If all connections fail due to user errors, availability is 100%.
 - If there are no connection attempts, availability is 100%.
 - If all connections fail due to system errors, availability is 0%.
-- Currently, availability metric data is not yet supported for the serverless compute tier and will be displayed as 100%.
 
 Availability metric is therefore a composite metric derived from following existing metrics:
 
@@ -102,7 +101,8 @@ User errors include all connections that fail due to user configuration, workloa
 
 - Examples of errors caused by user workload:
     - [Connection failure due to resource governance](troubleshoot-common-errors-issues.md?view=azuresql-db&preserve-view=true#resource-governance-errors)
-
+    - Connection attempts to a serverless database that is in a paused state
+    
 - Examples of errors caused by user management:
     - Scaling up or down the database or elastic pool
     - Geo replication planned or forced failover

docs/t-sql/statements/create-columnstore-index-transact-sql.md

@@ -4,7 +4,7 @@ description: CREATE COLUMNSTORE INDEX converts a rowstore table to a clustered c
 author: markingmyname
 ms.author: maghan
 ms.reviewer: randolphwest
-ms.date: 03/04/2025
+ms.date: 04/11/2025
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -157,6 +157,13 @@ For more detail on feature availability, see [What's new in columnstore indexes]
 
 Create a clustered columnstore index in which all of the data is compressed and stored by column. The index includes all of the columns in the table, and stores the entire table. If the existing table is a heap or clustered index, then it is converted to a clustered columnstore index. If the table is already stored as a clustered columnstore index, then the existing index is dropped and rebuilt.
 
+> [!IMPORTANT]
+> In SQL database in Fabric, a clustered columnstore index must be created within the same batch or transaction as the table it belongs to. Adding a clustered columnstore index to a table after it has already been created can result in the following error:
+>
+> ```output
+> Msg 35354, Level 16, State 1, Line 63, The statement failed because a clustered columnstore index cannot be created on a table enabled for Change Feed. Consider disabling Change Feed and then creating the clustered columnstore index.
+> ```
+
 #### *index_name*
 
 Specifies the name for the new index.