20210819 1358 update sp_helptext for azure synapse

Author: WilliamDAssafMSFT

docs/relational-databases/security/metadata-visibility-configuration.md

@@ -1,8 +1,8 @@
 ---
-title: "Metadata Visibility Configuration | Microsoft Docs"
+title: "Metadata Visibility Configuration"
 description: Learn how to configure metadata visibility for securables that a user owns or has been granted permission to in SQL Server.
 ms.custom: ""
-ms.date: "03/17/2017"
+ms.date: "08/19/2021"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database, synapse-analytics, pdw"
 ms.reviewer: ""
@@ -17,7 +17,6 @@ helpviewer_keywords:
   - "displaying metadata"
   - "database metadata [SQL Server]"
   - "metadata [SQL Server], permissions"
-ms.assetid: 50d2e015-05ae-4014-a1cd-4de7866ad651
 author: VanMSFT
 ms.author: vanto
 monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current"
@@ -86,7 +85,7 @@ GO
 
  SQL modules, such as stored procedures and triggers, run under the security context of the caller and, therefore, have limited metadata accessibility. For example, in the following code, when the stored procedure tries to access metadata for the table `myTable` on which the caller has no rights, an empty result set is returned. In earlier releases of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], a row is returned.  
 
-```  
+```sql  
 CREATE PROCEDURE assumes_caller_can_access_metadata  
 BEGIN  
 SELECT name, object_id   
@@ -103,7 +102,7 @@ GO
 > [!NOTE]  
 >  The following example uses the [sys.objects](../../relational-databases/system-catalog-views/sys-objects-transact-sql.md) catalog view instead of the [sys.sysobjects](../../relational-databases/system-compatibility-views/sys-sysobjects-transact-sql.md) compatibility view.  
   
-```  
+```sql  
 CREATE PROCEDURE does_not_assume_caller_can_access_metadata  
 WITH EXECUTE AS OWNER  
 AS  
@@ -125,7 +124,7 @@ GO
 
  The following metadata is not subject to forced disclosure:  
 
--   The value stored in the **provider_string** column of **sys.servers**. A user that does not have ALTER ANY LINKED SERVER permission will see a NULL value in this column.  
+-   The value stored in the `provider_string` column of `sys.servers`. A user that does not have ALTER ANY LINKED SERVER permission will see a NULL value in this column.  
 
 -   Source definition of a user-defined object such as a stored procedure or trigger. The source code is visible only when one of the following is true:  
 
@@ -135,17 +134,17 @@ GO
 
 -   The definition columns found in the following catalog views:  
 
-    - **sys.all_sql_modules**  
-    - **sys.server_sql_modules**  
-    - **sys.default_constraints**
-    - **sys.numbered_procedures**
-    - **sys.sql_modules**
-    - **sys.check_constraints**
-    - **sys.computed_columns**
+    - `sys.all_sql_modules`  
+    - `sys.server_sql_modules`  
+    - `sys.default_constraints`
+    - `sys.numbered_procedures`
+    - `sys.sql_modules`
+    - `sys.check_constraints`
+    - `sys.computed_columns`
 
--   The **ctext** column in the **syscomments** compatibility view.  
+-   The `ctext` column in the `syscomments` compatibility view.  
 
--   The output of the **sp_helptext** procedure.  
+-   The output of the `sp_helptext` procedure.  
 
 -   The following columns in the information schema views:
 
@@ -158,10 +157,13 @@ GO
 
 -   OBJECT_DEFINITION() function  
 
--   The value stored in the password_hash column of **sys.sql_logins**.  A user that does not have CONTROL SERVER permission will see a NULL value in this column.  
+-   The value stored in the password_hash column of `sys.sql_logins`.  A user that does not have CONTROL SERVER permission will see a NULL value in this column.  
 
 > [!NOTE]  
->  The SQL definitions of built-in system procedures and functions are publicly visible through the **sys.system_sql_modules** catalog view, the **sp_helptext** stored procedure, and the OBJECT_DEFINITION() function.  
+>  The SQL definitions of built-in system procedures and functions are publicly visible through the `sys.system_sql_modules` catalog view, the `sp_helptext` stored procedure, and the OBJECT_DEFINITION() function.  
+
+> [!NOTE]
+> The system stored procedure `sp_helptext` is not supported in Azure Synapse Analytics. Instead, use the `OBJECT_DEFINITION` system function or `sys.sql_modules` object catalog view.
   
 ## General Principles of Metadata Visibility  
  The following are some general principles to consider regarding metadata visibility:  
@@ -194,11 +196,12 @@ GO
  The visibility of subcomponents, such as indexes, check constraints, and triggers is determined by permissions on the parent. These subcomponents do not have grantable permissions. For example, if a user has been granted some permission on a table, the user can view the metadata for the tables, columns, indexes, check constraints, triggers, and other such subcomponents.  Another example is granting SELECT on only an individual column of a given table: this will allow the grantee to view the matadata of the whole table, including all columns. One way to think of it, is that the VIEW DEFINITION permission only works on entity-level (the table in this case) and is not available for Sub-entity lists (such as column or security expressions).
 
 The following code demonstrates this behavior:
+
 ```sql
 CREATE TABLE t1
 (
-	c1 int,
-	c2 varchar
+    c1 int,
+    c2 varchar
  );
 GO
 CREATE USER testUser WITHOUT LOGIN;

docs/relational-databases/stored-procedures/view-the-definition-of-a-stored-procedure.md

@@ -1,8 +1,8 @@
 ---
-title: "View the Definition of a Stored Procedure | Microsoft Docs"
+title: "View the Definition of a Stored Procedure"
 description: Learn how to view the definition of procedure in Object Explorer and by using a system stored procedure, system function, and object catalog view in the Query Editor.
 ms.custom: ""
-ms.date: "03/14/2017"
+ms.date: "08/19/2021"
 ms.prod: sql
 ms.technology: stored-procedures
 ms.reviewer: ""
@@ -12,7 +12,6 @@ helpviewer_keywords:
   - "definition of stored procedure"
   - "viewing stored procedures"
   - "displaying stored procedures"
-ms.assetid: 93318587-a0c5-4788-946f-3b5dc8372ea9
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current"
@@ -41,6 +40,9 @@ This topic describes how to view the definition of procedure in Object Explorer
 
  Object Catalog View: **sys.sql_modules**  
  The visibility of the metadata in catalog views is limited to securables that a user either owns or on which the user has been granted some permission. For more information, see [Metadata Visibility Configuration](../../relational-databases/security/metadata-visibility-configuration.md).  
+
+> [!NOTE]
+> The system stored procedure `sp_helptext` is not supported in Azure Synapse Analytics. Instead, use `OBJECT_DEFINITION` system function or `sys.sql_modules` object catalog view. Samples are provided later in this article.
   
 ##  <a name="Procedures"></a> How to View the Definition of a Stored Procedure  
  You can use one of the following:  
@@ -61,47 +63,50 @@ This topic describes how to view the definition of procedure in Object Explorer
 4.  Select **New Query Editor Window**. This will display the procedure definition.  
 
 ###  <a name="TsqlProcedure"></a> Using Transact-SQL  
- **To view the definition of a procedure in Query Editor**  
+
+#### To view the definition of a procedure in Query Editor
 
  System Stored Procedure: **sp_helptext**  
  1.  In Object Explorer, connect to an instance of the [!INCLUDE[ssDE](../../includes/ssde-md.md)].  
 
 2.  On the toolbar, click **New Query**.  
 
-3.  In the query window, enter the following statement that uses the **sp_helptext** system stored procedure. Change the database name and stored procedure name to reference the database and stored procedure that you want.  
+3.  In the query window, enter the following statement that uses the `sp_helptext` system stored procedure. Change the database name and stored procedure name to reference the database and stored procedure that you want.  
 
-    ```  
+    ```sql  
     USE AdventureWorks2012;  
     GO  
     EXEC sp_helptext N'AdventureWorks2012.dbo.uspLogError';  
     ```  
 
- System Function: **OBJECT_DEFINITION**  
+#### System Function: **OBJECT_DEFINITION**  
+
  1.  In Object Explorer, connect to an instance of the [!INCLUDE[ssDE](../../includes/ssde-md.md)].  
 
 2.  On the toolbar, click **New Query**.  
 
-3.  In the query window, enter the following statements that use the **OBJECT_DEFINITION** system function. Change the database name and stored procedure name to reference the database and stored procedure that you want.  
+3.  In the query window, enter the following statements that use the `OBJECT_DEFINITION` system function. Change the database name and stored procedure name to reference the database and stored procedure that you want.  
 
-    ```  
+    ```sql  
     USE AdventureWorks2012;  
     GO  
     SELECT OBJECT_DEFINITION (OBJECT_ID(N'AdventureWorks2012.dbo.uspLogError'));  
     ```  
 
- Object Catalog View: **sys.sql_modules**  
+#### <a id=sql_modules></a> Object Catalog View: **sys.sql_modules**  
+
  1.  In Object Explorer, connect to an instance of the [!INCLUDE[ssDE](../../includes/ssde-md.md)].  
 
 2.  On the toolbar, click **New Query**.  
 
-3.  In the query window, enter the following statements that use the **sys.sql_modules** catalog view. Change the database name and stored procedure name to reference the database and stored procedure that you want.  
+3.  In the query window, enter the following statements that use the `sys.sql_modules` catalog view. Change the database name and stored procedure name to reference the database and stored procedure that you want.  
 
-    ```  
+    ```sql  
     USE AdventureWorks2012;  
     GO  
-    SELECT definition  
+    SELECT [definition]
     FROM sys.sql_modules  
-    WHERE object_id = (OBJECT_ID(N'AdventureWorks2012.dbo.uspLogError'));  
+    WHERE object_id = (OBJECT_ID(N'dbo.uspLogError'));  
     ```  
 
 ## See Also  

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

@@ -1,8 +1,8 @@
 ---
 description: "sp_helptext (Transact-SQL)"
-title: "sp_helptext (Transact-SQL) | Microsoft Docs"
+title: "sp_helptext (Transact-SQL)"
 ms.custom: ""
-ms.date: "03/14/2017"
+ms.date: "08/19/2021"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
 ms.reviewer: ""
@@ -15,7 +15,6 @@ dev_langs:
   - "TSQL"
 helpviewer_keywords: 
   - "sp_helptext"
-ms.assetid: 24135456-05f0-427c-884b-93cf38dd47a8
 author: markingmyname
 ms.author: maghan
 monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current"
@@ -51,7 +50,10 @@ sp_helptext [ @objname = ] 'name' [ , [ @columnname = ] computed_column_name ]
 |**Text**|**nvarchar(255)**|Object definition|  
 
 ## Remarks  
- sp_helptext displays the definition that is used to create an object in multiple rows. Each row contains 255 characters of the [!INCLUDE[tsql](../../includes/tsql-md.md)] definition. The definition resides in the **definition** column in the [sys.sql_modules](../../relational-databases/system-catalog-views/sys-sql-modules-transact-sql.md) catalog view.  
+ sp_helptext displays the definition that is used to create an object in multiple rows. Each row contains 255 characters of the [!INCLUDE[tsql](../../includes/tsql-md.md)] definition. The definition resides in the `definition` column in the [sys.sql_modules](../../relational-databases/system-catalog-views/sys-sql-modules-transact-sql.md) catalog view.  
+
+> [!NOTE]
+> The system stored procedure `sp_helptext` is not supported in Azure Synapse Analytics. Instead, use `OBJECT_DEFINITION` system function or `sys.sql_modules` object catalog view for equivalent results.
   
 ## Permissions  
  Requires membership in the **public** role. System object definitions are publicly visible. The definition of user objects is visible to the object owner or grantees that have any one of the following permissions: ALTER, CONTROL, TAKE OWNERSHIP, or VIEW DEFINITION.  
@@ -61,7 +63,7 @@ sp_helptext [ @objname = ] 'name' [ , [ @columnname = ] computed_column_name ]
 ### A. Displaying the definition of a trigger  
  The following example displays the definition of the trigger `dEmployee` in the [!INCLUDE[ssSampleDBobject](../../includes/sssampledbobject-md.md)]database.  
 
-```  
+```sql  
 USE AdventureWorks2012;  
 GO  
 EXEC sp_helptext 'HumanResources.dEmployee';  
@@ -71,7 +73,7 @@ GO
 ### B. Displaying the definition of a computed column  
  The following example displays the definition of the computed column `TotalDue` on the `SalesOrderHeader` table in the [!INCLUDE[ssSampleDBobject](../../includes/sssampledbobject-md.md)] database.  
 
-```  
+```sql  
 USE AdventureWorks2012;  
 GO  
 sp_helptext @objname = N'AdventureWorks2012.Sales.SalesOrderHeader', @columnname = TotalDue ;  

docs/relational-databases/views/get-information-about-a-view.md

@@ -1,8 +1,8 @@
 ---
 description: "Get Information About a View"
-title: "Get Information About a View | Microsoft Docs"
+title: "Get Information About a View"
 ms.custom: ""
-ms.date: "03/14/2017"
+ms.date: "08/19/2021"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database, synapse-analytics, pdw"
 ms.reviewer: ""
@@ -19,7 +19,6 @@ helpviewer_keywords:
   - "viewing view information"
   - "status information [SQL Server], views"
   - "view dependencies"
-ms.assetid: 05a73e33-8f85-4fb6-80c1-1b659e753403
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current"
@@ -182,7 +181,7 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 
 3.  Copy and paste one of the following examples into the query window and click **Execute**.  
 
-    ```  
+    ```sql  
     USE AdventureWorks2012;  
     GO  
     SELECT definition, uses_ansi_nulls, uses_quoted_identifier, is_schema_bound  
@@ -191,18 +190,21 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
     GO  
     ```  
 
-    ```  
+    ```sql  
     USE AdventureWorks2012;   
     GO  
     SELECT OBJECT_DEFINITION (OBJECT_ID('HumanResources.vEmployee')) AS ObjectDefinition;   
     GO  
     ```  
 
-    ```  
+    ```sql  
     EXEC sp_helptext 'HumanResources.vEmployee';  
     ```  
 
  For more information, see [sys.sql_modules (Transact-SQL)](../../relational-databases/system-catalog-views/sys-sql-modules-transact-sql.md), [OBJECT_DEFINITION (Transact-SQL)](../../t-sql/functions/object-definition-transact-sql.md) and [sp_helptext (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-helptext-transact-sql.md).  
+
+> [!NOTE]
+> The system stored procedure `sp_helptext` is not supported in Azure Synapse Analytics. Instead, use the `OBJECT_DEFINITION` system function or `sys.sql_modules` object catalog view.
 
 #### To get the dependencies of a view  
 
@@ -212,7 +214,7 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 
 3.  Copy and paste the following example into the query window and click **Execute**.  
 
-    ```  
+    ```sql  
     USE AdventureWorks2012;  
     GO  
     SELECT OBJECT_NAME(referencing_id) AS referencing_entity_name,