Merge pull request #6793 from swanderz/patch-2

qualify sp_renames support in Azure Synapse

Author: ktoliver

docs/relational-databases/system-stored-procedures/sp-rename-transact-sql.md

@@ -29,7 +29,8 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
   Changes the name of a user-created object in the current database. This object can be a table, index, column, alias data type, or [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[dnprdnshort](../../includes/dnprdnshort-md.md)] common language runtime (CLR) user-defined type.  
 
 > [!NOTE]
-> In [!INCLUDE[ssazuresynapse](../../includes/ssazuresynapse_md.md)], sp_rename is in **Preview** and can only be used to rename a COLUMN in a user object in the **dbo** schema.
+> In [!INCLUDE[ssazuresynapse](../../includes/ssazuresynapse_md.md)], sp_rename is in **Preview** for dedicated SQL pools and can only be used to rename a COLUMN in a user object in the **dbo** schema.
+
 
 > [!CAUTION]  
 > Changing any part of an object name can break scripts and stored procedures. We recommend you do not use this statement to rename stored procedures, triggers, user-defined functions, or views; instead, drop the object and re-create it with the new name.  
@@ -220,7 +221,8 @@ sp_rename 'Person.Person.ContactMail1', 'NewContact','Statistics';
  The following example renames the `c1` column in the `table1` table to `col1`. 
 
 > [!NOTE]
-> This [!INCLUDE[ssazuresynapse](../../includes/ssazuresynapse_md.md)] feature is still in preview and is currently available only for objects in the **dbo** schema. 
+> This [!INCLUDE[ssazuresynapse](../../includes/ssazuresynapse_md.md)] feature is still in preview for dedicated SQL pools and is currently available only for objects in the **dbo** schema. 
+
 
 ```sql  
 CREATE TABLE table1 (c1 INT, c2 INT);