Resolving script issues and old keys

Author: whhender

articles/synapse-analytics/sql/create-external-table-as-select.md

@@ -5,7 +5,7 @@ author: vvasic-msft
 ms.service: azure-synapse-analytics
 ms.topic: overview
 ms.subservice: sql
-ms.date: 04/15/2020
+ms.date: 02/20/2025
 ms.author: vvasic
 ms.reviewer: whhender 
 ---
@@ -16,28 +16,31 @@ In this article, you'll learn how to store query results to storage using server
 
 ## Prerequisites
 
-Your first step is to **create a database** where you will execute the queries. Then initialize the objects by executing [setup script](https://github.com/Azure-Samples/Synapse/blob/master/SQL/Samples/LdwSample/SampleDB.sql) on that database. This setup script will create the data sources, database scoped credentials, and external file formats that are used to read data in these samples.
+Your first step is to **create a database** where you'll execute the queries. Then initialize the objects by executing [setup script](https://github.com/Azure-Samples/Synapse/blob/master/SQL/Samples/LdwSample/SampleDB.sql) on that database. This setup script will create the data sources, database scoped credentials, and external file formats that are used to read data in these samples.
 
 Follow the instructions in this article to create data sources, database scoped credentials, and external file formats that are used to write data into the output storage.
 
 ## Create external table as select
 
-You can use the CREATE EXTERNAL TABLE AS SELECT (CETAS) statement to store the query results to  storage.
+You can use the CREATE EXTERNAL TABLE AS SELECT (CETAS) statement to store the query results to storage.
 
 > [!NOTE]
-> Change the first line in the query, i.e., [mydbname], so you're using the database you created.
+> Change these values in the query to reflect your environment:
+> - mydbname - change it to the name of the database you created
+> - storage-account-sas - the [shared access signature](/azure/ai-services/document-intelligence/authentication/create-sas-tokens#generating-sas-tokens) for a storage account where you want to write your results
+> - your-storage-account-name - the name of your storage account where you want to write your results (Make sure you have a container called 'csv' or that you change the name of the container here also)
 
 ```sql
 USE [mydbname];
 GO
 
 CREATE DATABASE SCOPED CREDENTIAL [SasTokenWrite]
 WITH IDENTITY = 'SHARED ACCESS SIGNATURE',
-     SECRET = 'sv=2018-03-28&ss=bfqt&srt=sco&sp=rwdlacup&se=2019-04-18T20:42:12Z&st=2019-04-18T12:42:12Z&spr=https&sig=lQHczNvrk1KoYLCpFdSsMANd0ef9BrIPBNJ3VYEIq78%3D';
+     SECRET = 'storage-account-sas';
 GO
 
 CREATE EXTERNAL DATA SOURCE [MyDataSource] WITH (
-    LOCATION = 'https://<storage account name>.blob.core.windows.net/csv', CREDENTIAL = [SasTokenWrite]
+    LOCATION = 'https://your-storage-account-name.blob.core.windows.net/csv', CREDENTIAL = [SasTokenWrite]
 );
 GO
 
@@ -69,14 +72,14 @@ FROM
 ```
 
 > [!NOTE]
-> You must modify this script and change the target location to execute it again. External tables cannot be created on the location where you already have some data.
+> You must modify this script and change the target location to execute it again. External tables can't be created on the location where you already have some data.
 
 ## Use the external table
 
 You can use the external table created through CETAS like a regular external table.
 
 > [!NOTE]
-> Change the first line in the query, i.e., [mydbname], so you're using the database you created.
+> Change the first line in the query, that is, [mydbname], so you're using the database you created.
 
 ```sql
 USE [mydbname];
@@ -93,14 +96,10 @@ ORDER BY
 
 ## Remarks
 
-Once you store your results, the data in the external table cannot be modified. You cannot repeat this script because CETAS will not overwrite the underlying data created in the previous execution. Vote for the following feedback items if some of these are required in your scenarios, or propose the new ones on Azure feedback site:
-- [Enable inserting new data into external table](https://feedback.azure.com/d365community/forum/9b9ba8e4-0825-ec11-b6e6-000d3a4f07b8)
-- [Enable deleting data from external table](https://feedback.azure.com/d365community/idea/fb5a00c9-0a25-ec11-b6e6-000d3a4f07b8)
-- [Specify partitions in CETAS](https://feedback.azure.com/d365community/idea/e28278db-0a25-ec11-b6e6-000d3a4f07b8)
-- [Specify file sizes and counts](https://feedback.azure.com/d365community/idea/262048b9-0925-ec11-b6e6-000d3a4f07b8)
+Once you store your results, the data in the external table can't be modified. You can't repeat this script because CETAS won't overwrite the underlying data created in the previous execution.
 
-The only supported output types are Parquet and CSV. You can vote for the other types on [Azure feedback site](https://feedback.azure.com/d365community/forum/9b9ba8e4-0825-ec11-b6e6-000d3a4f07b8).
+The only supported output types are currently Parquet and CSV.
 
-## Next steps
+## Related content
 
 For more information on how to query different file types, see the [Query single CSV file](query-single-csv-file.md), [Query Parquet files](query-parquet-files.md), and [Query JSON files](query-json-files.md) articles.

articles/synapse-analytics/sql/create-use-external-tables.md

@@ -41,7 +41,7 @@ Your first step is to create a database where the tables will be created. Before
     ```sql
     CREATE DATABASE SCOPED CREDENTIAL [sqlondemand]
     WITH IDENTITY='SHARED ACCESS SIGNATURE',  
-    SECRET = 'sv=2018-03-28&ss=bf&srt=sco&sp=rl&st=2019-10-14T12%3A10%3A25Z&se=2061-12-31T12%3A10%3A00Z&sig=KlSU2ullCscyTS0An0nozEpo4tO5JAgGBvw%2FJX2lguw%3D'
+    SECRET = 'sv=2022-11-02&ss=b&srt=co&sp=rl&se=2042-11-26T17:40:55Z&st=2024-11-24T09:40:55Z&spr=https&sig=DKZDuSeZhuCWP9IytWLQwu9shcI5pTJ%2Fw5Crw6fD%2BC8%3D'
     ```
 
 - EXTERNAL DATA SOURCE `sqlondemanddemo` that references demo storage account protected with SAS key, and EXTERNAL DATA SOURCE `nyctlc` that references publicly available Azure storage account on location `https://azureopendatastorage.blob.core.windows.net/nyctlc/`.

articles/synapse-analytics/sql/develop-tables-external-tables.md

@@ -84,7 +84,7 @@ The following example creates a Hadoop external data source in dedicated SQL poo
 ```sql
 CREATE DATABASE SCOPED CREDENTIAL [ADLS_credential]
 WITH IDENTITY='SHARED ACCESS SIGNATURE',  
-SECRET = 'sv=2018-03-28&ss=bf&srt=sco&sp=rl&st=2019-10-14T12%3A10%3A25Z&se=2061-12-31T12%3A10%3A00Z&sig=KlSU2ullCscyTS0An0nozEpo4tO5JAgGBvw%2FJX2lguw%3D'
+SECRET = 'sv=2022-11-02&ss=b&srt=co&sp=rl&se=2042-11-26T17:40:55Z&st=2024-11-24T09:40:55Z&spr=https&sig=DKZDuSeZhuCWP9IytWLQwu9shcI5pTJ%2Fw5Crw6fD%2BC8%3D'
 GO
 CREATE EXTERNAL DATA SOURCE AzureDataLakeStore
 WITH
@@ -110,7 +110,7 @@ The following example creates an external data source in serverless or dedicated
 ```sql
 CREATE DATABASE SCOPED CREDENTIAL [sqlondemand]
 WITH IDENTITY='SHARED ACCESS SIGNATURE',  
-SECRET = 'sv=2018-03-28&ss=bf&srt=sco&sp=rl&st=2019-10-14T12%3A10%3A25Z&se=2061-12-31T12%3A10%3A00Z&sig=KlSU2ullCscyTS0An0nozEpo4tO5JAgGBvw%2FJX2lguw%3D'
+SECRET = 'sv=2022-11-02&ss=b&srt=co&sp=rl&se=2042-11-26T17:40:55Z&st=2024-11-24T09:40:55Z&spr=https&sig=DKZDuSeZhuCWP9IytWLQwu9shcI5pTJ%2Fw5Crw6fD%2BC8%3D'
 GO
 CREATE EXTERNAL DATA SOURCE SqlOnDemandDemo WITH (
     LOCATION = 'https://sqlondemandstorage.blob.core.windows.net',