Merge pull request #53416 from JulianePadrao/update-azure-data-studio

Remove references to Azure Data Studio in Learn modules due to deprecation

Author: JamesJBarnett

learn-pr/wwl-data-ai/create-stored-procedures-table-valued-functions/includes/3-pass-parameters-to.md

@@ -40,7 +40,7 @@ EXEC customers.customerid GETDATE()
 
 Check that parameters are of the correct data type. For example, if a procedure accepts an NVARCHAR, pass in the Unicode character string format: **N'string'**.
 
-You can view parameter names and data types in Azure Data Studio or SQL Server Management Studio (SSMS). Expand the list of database objects until you see the **Stored Procedures** folder, beneath the **Programmability** folder.
+You can view parameter names and data types in SQL Server Management Studio (SSMS). Expand the list of database objects until you see the **Stored Procedures** folder, beneath the **Programmability** folder.
 
 :::image type="content" source ="../media/parameter.png" alt-text ="Diagram showing the Expand the Programming folder to view stored procedures and parameter data types.":::
 

learn-pr/wwl-data-ai/explore-security-practices-azure-sql-database/includes/4-understand-firewall-rules.md

@@ -25,7 +25,7 @@ Database-level IP firewall rules allow clients to access specific databases by c
 
 When connecting to a database with database-level firewall rules enabled, Azure SQL Database first checks for a database-level firewall rule matching the database name in the connection string. If no such rule exists, it then checks the server-level IP firewall rules, which apply to all databases on the server. If either rule is found, the connection is completed.
 
-If neither exist and the user is connecting through SQL Server Management Studio or Azure Data Studio, they'll be prompted to create a firewall rule as shown below.
+If neither exist and the user is connecting through SQL Server Management Studio, they'll be prompted to create a firewall rule as shown below.
 
 :::image type="content" source="../media/4-firewall-rule.png" alt-text="Screenshot of the New Firewall Rule dialog in SQL Server Management Studio.":::
 

learn-pr/wwl-data-ai/get-started-transact-sql-programming/includes/3-describe-batches.md

@@ -1,10 +1,10 @@
 T-SQL batches are collections of one or more T-SQL statements that are submitted to SQL Server by a client as a single unit. SQL Server operates on all the statements in a batch at the same time when parsing, optimizing, and executing the code.
 
-If you're a report writer who typically writes queries using SELECT statements and not procedures, it's still important to understand batch boundaries. These boundaries will affect your work with variables and parameters in stored procedures and other routines. For example, a variable must be declared in the same batch in which it's referenced. It's important, therefore, to recognize what is contained in a batch.
+If you're a report writer who typically writes queries using `SELECT` statements and not procedures, it's still important to understand batch boundaries. These boundaries affect your work with variables and parameters in stored procedures and other routines. For example, a variable must be declared in the same batch in which it's referenced. It's important, therefore, to recognize what is contained in a batch.
 
-Batches are delimited by the client application. How you mark the end of a batch depends on the settings of your client. For Microsoft clients including SQL Server Management Studio (SSMS), Azure Data Studio, and SQLCMD the keyword is GO.
+Batches are delimited by the client application. How you mark the end of a batch depends on the settings of your client. For Microsoft clients including SQL Server Management Studio (SSMS) and SQLCMD the keyword is `GO`.
 
-In this example, there are two distinct batches each terminated with a GO:
+In this example, there are two distinct batches each terminated with a `GO` statement:
 
 ```sql
 CREATE NEW <view_name>
@@ -17,16 +17,16 @@ GO
 
 The batch terminator **GO** isn't a T-SQL keyword, but is one recognized by SSMS to indicate the end of a batch.
 
-When working with T-SQL batches, there are two important considerations to keep in mind:
+Keep two important considerations in mind when you work with T-SQL batches:
 
-- Batches are boundaries for variable scope, which means a variable defined in one batch may only be referenced by other code in the same batch
-- Some statements, typically data definition statements such as CREATE VIEW, CREATE FUNCTION, and CREATE PROCEDURE may not be combined with others in the same batch.
+- Batches are boundaries for variable scope, which means a variable defined in one batch can only be referenced by other code in the same batch
+- Some statements, typically data definition statements such as `CREATE VIEW`, `CREATE FUNCTION`, and `CREATE PROCEDURE` can't be combined with others in the same batch.
 
 ## Working with batches
 
-A batch is a collection of T-SQL statements submitted to SQL Server for parsing and execution. Understanding how batches are parsed will be useful in identifying error messages and behavior.  When a batch is submitted by a client, such as when you press the Execute button in SSMS, the batch is parsed for syntax errors by the SQL Server engine. Any errors found will cause the entire batch to be rejected; there will be no partial execution of statements within the batch.
+A batch is a collection of T-SQL statements submitted to SQL Server for parsing and execution. Understanding how batches are parsed is useful in identifying error messages and behavior. When a batch is submitted by a client, such as when you press the Execute button in SSMS, the batch is parsed for syntax errors by the SQL Server engine. Any errors found cause the entire batch to be rejected; there is no partial execution of statements within the batch.
 
-If the batch passes the syntax check, then SQL Server runs other steps, resolving object names, checking permissions, and optimizing the code for execution. Once this process completes and execution begins, statements succeed or fail individually. This is an important contrast to syntax checking. When a runtime error occurs on one line, the next line may be executed, unless you've added error handling to the code.
+If the batch passes the syntax check, then SQL Server runs other steps, resolving object names, checking permissions, and optimizing the code for execution. Once this process completes and execution begins, statements succeed or fail individually. This is an important contrast to syntax checking. When a runtime error occurs on one line, the next line can still execute, unless you add error handling to the code.
 
 For example, the following batch contains a syntax error:
 
@@ -43,14 +43,14 @@ Msg 102, Level 15, State 1, Line 1
 Incorrect syntax near 'VALUE'.
 ```
 
-The error occurred in line 1, but the entire batch is rejected, and execution doesn't continue with line 2. Even if each of the INSERT statements were reversed and the syntax error occurred in the second line, the first line wouldn't be executed because the entire batch would be rejected.
+The error occurred in line 1, but the entire batch is rejected, and execution doesn't continue with line 2. Even if each of the `INSERT` statements were reversed and the syntax error occurred in the second line, the frontline wouldn't be executed because the entire batch would be rejected.
 
-Using the previous example, this batch doesn't contain an error:
+In contrast, this corrected batch doesn't contain an error:
 
 ```sql
 INSERT INTO dbo.t1 VALUES(1,2,N'abc');
 INSERT INTO dbo.t1 VALUES(2,3,N'def');
 GO
 ```
 
-In the previous samples, we've used INSERT statements rather than SELECT because it's more common for modification statements to be grouped in batches than SELECT statements.
+The previous samples use `INSERT` statements rather than `SELECT` because modification statements are more commonly grouped in batches.

learn-pr/wwl-data-ai/orchestrate-data-movement-transformation-azure-data-factory/includes/6-execute-packages.md

@@ -5,6 +5,6 @@ An Azure-SSIS IR supports:
 * Running packages that are or to be deployed into SSIS catalog (SSISDB) hosted by your Azure SQL Database server or Managed Instance in Project Deployment Model
 * Running packages that are or to be deployed into file system, Azure Files, or SQL Server database (MSDB) hosted by your Azure SQL Managed Instance in Package Deployment Model
 
-After the Azure-SSIS IR is provisioned, the same familiar tools for deployment and running the packages in Azure can be used. Most of the familiar tools such as SQL Server Data Tools (SSDT), SQL Server Management Studio (SSMS), Azure Data Studio, and command-line utilities are Azure-enabled, and therefore ready to be used.
+After the Azure-SSIS IR is provisioned, the same familiar tools for deployment and running the packages in Azure can be used. Most of the familiar tools such as SQL Server Data Tools (SSDT), SQL Server Management Studio (SSMS) and command-line utilities are Azure-enabled, and therefore ready to be used.
 
 Using SSDT allows you to check and assess the Azure Cloud compatibility with Azure-SSIS Integration Runtime in Azure Data Factory of the SSIS packages you might already be running locally. This feature comes in handy when you want to test existing packages before an actual lift and shift or migration can take place to Azure. If you want to develop new packages to run in Azure, it's also good to test them with this feature.

learn-pr/wwl-data-ai/protect-data-transit-rest/includes/3-configure-server-and-database-firewall.md

@@ -25,7 +25,7 @@ Database-level firewall rules are configured through T-SQL only using the `sp_se
 
 Upon connection, Azure SQL Database first checks for a database-level firewall rule corresponding to the database name specified in the connection string. If no such rule exists, the firewall then checks the server-level IP firewall rules. Server-level IP firewall rules apply to all databases on the server. If a matching rule is found at either level, the connection is established.
 
-If neither exist and the user is connecting through SQL Server Management Studio or Azure Data Studio, they'll be prompted to create a firewall rule.
+If neither exist and the user is connecting through SQL Server Management Studio, they'll be prompted to create a firewall rule.
 
 :::image type="content" source="../media/module-33-security-final-15.png" alt-text="New Firewall Rule Screen from SQL Server Management Studio.":::