Skip to content

Commit 81262b6

Browse files
committed
[BULK] Replace tsql with sql in code fence
1 parent 2889d72 commit 81262b6

File tree

4 files changed

+9
-9
lines changed

4 files changed

+9
-9
lines changed

articles/azure-arc/data/managed-instance-high-availability.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -183,7 +183,7 @@ Example output:
183183

184184
You can connect to the above primary endpoint using SQL Server Management Studio and verify using DMVs as:
185185

186-
```tsql
186+
```sql
187187
SELECT * FROM sys.dm_hadr_availability_replica_states
188188
```
189189

articles/data-lake-store/data-lake-store-data-transfer-sql-sqoop.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Before you begin, you must have the following:
3434

3535
**Create Table1**
3636

37-
```tsql
37+
```sql
3838
CREATE TABLE [dbo].[Table1](
3939
[ID] [int] NOT NULL,
4040
[FName] [nvarchar](50) NOT NULL,
@@ -49,7 +49,7 @@ Before you begin, you must have the following:
4949

5050
**Create Table2**
5151

52-
```tsql
52+
```sql
5353
CREATE TABLE [dbo].[Table2](
5454
[ID] [int] NOT NULL,
5555
[FName] [nvarchar](50) NOT NULL,
@@ -64,7 +64,7 @@ Before you begin, you must have the following:
6464

6565
1. Run the following command to add some sample data to **Table1**. Leave **Table2** empty. Later, you'll import data from **Table1** into Data Lake Storage Gen1. Then, you'll export data from Data Lake Storage Gen1 into **Table2**.
6666

67-
```tsql
67+
```sql
6868
INSERT INTO [dbo].[Table1] VALUES (1,'Neal','Kell'), (2,'Lila','Fulton'), (3, 'Erna','Myers'), (4,'Annette','Simpson');
6969
```
7070

@@ -134,7 +134,7 @@ An HDInsight cluster already has the Sqoop packages available. If you've configu
134134
135135
1. Verify that the data was uploaded to the SQL Database table. Use [SQL Server Management Studio](/azure/azure-sql/database/connect-query-ssms) or Visual Studio to connect to the Azure SQL Database and then run the following query.
136136
137-
```tsql
137+
```sql
138138
SELECT * FROM TABLE2
139139
```
140140

articles/search/search-howto-managed-identities-sql.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Follow the below steps to assign the search service or user-assigned managed ide
4242

4343
Include the brackets around your search service name or user-assigned managed identity name.
4444

45-
```tsql
45+
```sql
4646
CREATE USER [insert your search service name here or user-assigned managed identity name] FROM EXTERNAL PROVIDER;
4747
EXEC sp_addrolemember 'db_datareader', [insert your search service name here or user-assigned managed identity name];
4848
```
@@ -53,7 +53,7 @@ Follow the below steps to assign the search service or user-assigned managed ide
5353

5454
If you later change the search service identity or user-assigned identity after assigning permissions, you must remove the role membership and remove the user in the SQL database, then repeat the permission assignment. Removing the role membership and user can be accomplished by running the following commands:
5555

56-
```tsql
56+
```sql
5757
sp_droprolemember 'db_datareader', [insert your search service name or user-assigned managed identity name];
5858
5959
DROP USER IF EXISTS [insert your search service name or user-assigned managed identity name];

articles/search/search-index-azure-sql-managed-instance-with-managed-identity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ Follow these steps to assign the search service system managed identity permissi
5454
4. In the T-SQL window, copy the following commands and include the brackets around your search service name. Click on **Execute**.
5555

5656

57-
```tsql
57+
```sql
5858
CREATE USER [insert your search service name here or user-assigned managed identity name] FROM EXTERNAL PROVIDER;
5959
EXEC sp_addrolemember 'db_datareader', [insert your search service name here or user-assigned managed identity name];
6060
```
@@ -63,7 +63,7 @@ Follow these steps to assign the search service system managed identity permissi
6363

6464
If you later change the search service system identity after assigning permissions, you must remove the role membership and remove the user in the SQL database, then repeat the permission assignment. Removing the role membership and user can be accomplished by running the following commands:
6565

66-
```tsql
66+
```sql
6767
sp_droprolemember 'db_datareader', [insert your search service name or user-assigned managed identity name];
6868
6969
DROP USER IF EXISTS [insert your search service name or user-assigned managed identity name];

0 commit comments

Comments
 (0)