Skip to content

Commit 1c46fe4

Browse files
authored
Merge pull request #16139 from JKirsch1/revisedindentedcodeblocks1
1750982 | Repairing indented code blocks | 1 revised
2 parents 9b04571 + 5822323 commit 1c46fe4

18 files changed

Lines changed: 119 additions & 96 deletions

docs/relational-databases/in-memory-oltp/survey-of-initial-areas-in-in-memory-oltp.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -326,8 +326,10 @@ SET @mesg = CONCAT(@LatestSalesOrderId,
326326
PRINT @mesg;
327327
```
328328
329-
-- Here is the actual PRINT output:
330-
-- 2 = Latest SalesOrderId, for CustomerId = 42
329+
Here is the actual PRINT output:
330+
```output
331+
-- 2 = Latest SalesOrderId, for CustomerId = 42
332+
```
331333

332334

333335

docs/relational-databases/replication/merge/specify-merge-replication-properties.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -163,8 +163,8 @@ This topic describes how to specify the conflict tracking and resolution level f
163163

164164
At the Publisher on the publication database, execute [sp_addmergearticle (Transact-SQL)](../../../relational-databases/system-stored-procedures/sp-addmergearticle-transact-sql.md). Specify a value of **false** for `@delete_tracking`. For more information, see [Define an Article](../../../relational-databases/replication/publish/define-an-article.md).
165165

166-
> [!NOTE]
167-
> If the source table for an article is already published in another publication, the value of **delete_tracking** must be the same for both articles.
166+
> [!NOTE]
167+
> If the source table for an article is already published in another publication, the value of **delete_tracking** must be the same for both articles.
168168
169169
### Specify that deletes be ignored for an existing merge article
170170

docs/relational-databases/replication/publish/create-an-updatable-subscription-to-a-transactional-publication.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ Configure updatable subscriptions on the **Updatable Subscriptions** page of the
9595
* `sync tran` - enables the subscription for immediate updating.
9696
* `failover` - enables the subscription for immediate updating with queued updating as a failover option.
9797
> [!NOTE]
98-
> `failover` requires that the publication also be enabled for queued updating subscriptions.
98+
> `failover` requires that the publication also be enabled for queued updating subscriptions.
9999
100100
4. At the Subscriber, execute [sp_addpullsubscription_agent](../../../relational-databases/system-stored-procedures/sp-addpullsubscription-agent-transact-sql.md). Specify the following:
101101

@@ -144,7 +144,7 @@ Configure updatable subscriptions on the **Updatable Subscriptions** page of the
144144
* The Windows credentials under which the Distribution Agent at the Distributor runs for `@job_login` and `@job_password`.
145145

146146
> [!NOTE]
147-
> Connections made using Windows Integrated Authentication are always made using the Windows credentials specified by `@job_login` and `@job_password`. The Distribution Agent always makes the local connection to the Distributor using Windows Integrated Authentication. By default, the agent will connect to the Subscriber using Windows Integrated Authentication.
147+
> Connections made using Windows Integrated Authentication are always made using the Windows credentials specified by `@job_login` and `@job_password`. The Distribution Agent always makes the local connection to the Distributor using Windows Integrated Authentication. By default, the agent will connect to the Subscriber using Windows Integrated Authentication.
148148
149149
* (Optional) A value of `0` for `@subscriber_security_mode` and the SQL Server login information for `@subscriber_login` and `@subscriber_password`, if you need to use SQL Server Authentication when connecting to the Subscriber.
150150
* A schedule for the Distribution Agent job for this subscription.
@@ -174,7 +174,7 @@ Configure updatable subscriptions on the **Updatable Subscriptions** page of the
174174
* `queued failover` - enables support for queued updating with immediate updating as a failover option.
175175

176176
> [!NOTE]
177-
> `queued failover` requires that the publication also be enabled for immediate updating subscriptions. To fail over to immediate updating, you must use [sp_link_publication](../../../relational-databases/system-stored-procedures/sp-link-publication-transact-sql.md) to define the credentials under which changes at the Subscriber are replicated to the Publisher.
177+
> `queued failover` requires that the publication also be enabled for immediate updating subscriptions. To fail over to immediate updating, you must use [sp_link_publication](../../../relational-databases/system-stored-procedures/sp-link-publication-transact-sql.md) to define the credentials under which changes at the Subscriber are replicated to the Publisher.
178178
179179
4. At the Subscriber, execute [sp_addpullsubscription_agent](../../../relational-databases/system-stored-procedures/sp-addpullsubscription-agent-transact-sql.md). Specify the following parameters:
180180

docs/relational-databases/security/encryption/always-encrypted-query-columns-ads.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -189,13 +189,15 @@ SELECT * FROM [dbo].[Patients]
189189
WHERE [SSN] = @SSN;
190190
```
191191

192-
Msg 402, Level 16, State 2, Line 5
193-
The data types char(11) encrypted with (encryption_type = 'DETERMINISTIC',
194-
encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1',
195-
column_encryption_key_database_name = 'Clinic') collation_name = 'Latin1_General_BIN2'
196-
and nchar(11) encrypted with (encryption_type = 'DETERMINISTIC',
197-
encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1',
198-
column_encryption_key_database_name = 'Clinic') are incompatible in the equal to operator.
192+
```output
193+
Msg 402, Level 16, State 2, Line 5
194+
The data types char(11) encrypted with (encryption_type = 'DETERMINISTIC',
195+
encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1',
196+
column_encryption_key_database_name = 'Clinic') collation_name = 'Latin1_General_BIN2'
197+
and nchar(11) encrypted with (encryption_type = 'DETERMINISTIC',
198+
encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1',
199+
column_encryption_key_database_name = 'Clinic') are incompatible in the equal to operator.
200+
```
199201

200202
> [!NOTE]
201203
> Without parameterization, the entire query, including type conversions is processed inside SQL Server/Azure SQL Database. With parameterization enabled, some type conversions are performed by Microsoft .NET Data Provider for SQL Server inside Azure Data Studio. Due to differences between the Microsoft .NET type system and the SQL Server type system (for example, different precision of some types, such as float), a query executed with parameterization enabled can produce different results than the query executed without parameterization enabled.

docs/relational-databases/security/encryption/always-encrypted-query-columns-ssms.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -198,13 +198,15 @@ SELECT * FROM [dbo].[Patients]
198198
WHERE [SSN] = @SSN;
199199
```
200200

201-
Msg 402, Level 16, State 2, Line 5
202-
The data types char(11) encrypted with (encryption_type = 'DETERMINISTIC',
203-
encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1',
204-
column_encryption_key_database_name = 'Clinic') collation_name = 'Latin1_General_BIN2'
205-
and nchar(11) encrypted with (encryption_type = 'DETERMINISTIC',
206-
encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1',
207-
column_encryption_key_database_name = 'Clinic') are incompatible in the equal to operator.
201+
```output
202+
Msg 402, Level 16, State 2, Line 5
203+
The data types char(11) encrypted with (encryption_type = 'DETERMINISTIC',
204+
encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1',
205+
column_encryption_key_database_name = 'Clinic') collation_name = 'Latin1_General_BIN2'
206+
and nchar(11) encrypted with (encryption_type = 'DETERMINISTIC',
207+
encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1',
208+
column_encryption_key_database_name = 'Clinic') are incompatible in the equal to operator.
209+
```
208210

209211
> [!NOTE]
210212
> Without parameterization, the entire query, including type conversions, is processed inside SQL Server/Azure SQL Database. With parameterization enabled, some type conversions are performed by .NET Framework inside SQL Server Management Studio. Due to differences between the .NET Framework type system and the SQL Server type system (e.g. different precision of some types, such as float), a query executed with parameterization enabled can produce different results than the query executed without parameterization enabled.

docs/relational-databases/system-dynamic-management-views/sys-dm-exec-sql-text-transact-sql.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ Execute the following T-SQL in a new query window in [!INCLUDE[ssManStudioFull](
104104
WAITFOR DELAY '00:02:00';
105105
```
106106
107-
2. Using **CROSS APPLY**.
107+
2. Using **CROSS APPLY**.
108108
The sql_handle from **sys.dm_exec_requests** will be passed to **sys.dm_exec_sql_text** using **CROSS APPLY**. Open a new query window and pass the spid identified in step 1. In this example the spid happens to be `59`.
109109

110110
```sql
@@ -114,7 +114,7 @@ Execute the following T-SQL in a new query window in [!INCLUDE[ssManStudioFull](
114114
WHERE session_id = 59 -- modify this value with your actual spid
115115
```
116116

117-
2. Passing **sql_handle** directly.
117+
2. Passing **sql_handle** directly.
118118
Acquire the **sql_handle** from **sys.dm_exec_requests**. Then, pass the **sql_handle** directly to **sys.dm_exec_sql_text**. Open a new query window and pass the spid identified in step 1 to **sys.dm_exec_requests**. In this example the spid happens to be `59`. Then pass the returned **sql_handle** as an argument to **sys.dm_exec_sql_text**.
119119

120120
```sql

docs/reporting-services/application-integration/integrating-reporting-services-using-reportviewer-controls-get-started.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -246,9 +246,9 @@ The Report Viewer Control is now shipped as a NuGet package and no longer shows
246246

247247
The viewer control is designed for modern browsers. The control may not work as expected if the browser renders the page using IE compatibility mode. Intranet sites may require a meta tag to override default browser behavior.
248248

249-
```
250-
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
251-
```
249+
```html
250+
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
251+
```
252252

253253
## NuGet.org pages
254254

docs/reporting-services/install-windows/add-an-additional-report-server-to-a-farm-ssrs-scale-out.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,9 @@ monikerRange: ">=sql-server-2016 <=sql-server-2016||=sqlallproducts-allversions"
6868

6969
If you configure all report servers with \<IsWebServiceEnable> set to False, you will see an error message similar to the following when you try to use [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] features:
7070

71-
The Reporting Services Web Service is not enabled. Configure at least one instance of the Reporting Services SharePoint Service to have <IsWebServiceEnable> set to true.
71+
```output
72+
The Reporting Services Web Service is not enabled. Configure at least one instance of the Reporting Services SharePoint Service to have <IsWebServiceEnable> set to true.
73+
```
7274

7375
For more information, see [Modify a Reporting Services Configuration File &#40;RSreportserver.config&#41;](../../reporting-services/report-server/modify-a-reporting-services-configuration-file-rsreportserver-config.md)
7476

docs/reporting-services/install-windows/install-the-first-report-server-in-sharepoint-mode.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -87,13 +87,17 @@ monikerRange: ">=sql-server-2016 <=sql-server-2016||=sqlallproducts-allversions"
8787
> [!NOTE]
8888
> Make sure you specify the correct name of the SharePoint server.
8989
90-
Set-SPServer SERVERNAME -Role Custom
90+
```powershell
91+
Set-SPServer SERVERNAME -Role Custom
92+
```
9193
9294
4. You should see a response that a timer job was scheduled. You will need to wait for the job to execute.
9395
9496
5. Use the following command to verify the server's assigned role.
9597
96-
Get-SPServer SERVERNAME
98+
```powershell
99+
Get-SPServer SERVERNAME
100+
```
97101
98102
6. The **Role** should list **Custom**.
99103
@@ -204,7 +208,9 @@ monikerRange: ">=sql-server-2016 <=sql-server-2016||=sqlallproducts-allversions"
204208
> [!IMPORTANT]
205209
> If you see an error message similar to the following:
206210
>
211+
```powershell
207212
> Install-SPRSService : The term 'Install-SPRSService' **is not recognized** as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
213+
```
208214
>
209215
> Either you are in the Windows Powershell instead of the SharePoint Management Shell or Reporting Services SharePoint mode is not installed. For more information on Reporting Services and PowerShell, see [PowerShell cmdlets for Reporting Services SharePoint Mode](../../reporting-services/report-server-sharepoint/powershell-cmdlets-for-reporting-services-sharepoint-mode.md).
210216

docs/reporting-services/mobile-reports/prepare-data-for-reporting-services-mobile-reports.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -18,14 +18,15 @@ ms.author: maggies
1818
## Date and time formats
1919
When dealing with date and time intervals for use in a mobile report, particularly with the TimeNavigator, it's important to format the date/time column properly so the [!INCLUDE[PRODUCT_NAME](../../includes/ss-mobilereptpub-short.md)] can identify it as such. Here are examples of valid date/time formats:
2020

21-
05/01/2009
22-
2009-05-01
23-
05/01/2009 14:57:32.8
24-
2009-05-01 14:57:32.8
25-
2009-05-01T14:57:32.8375298-04:00
26-
5/01/2008 14:57:32.80 -07:00
27-
1 May 2008 2:57:32.8 PM
28-
Fri, 15 May 2009 20:10:57 GMT
21+
`05/01/2009`
22+
`2009-05-01`
23+
`05/01/2009 14:57:32.8`
24+
`2009-05-01 14:57:32.8`
25+
`2009-05-01T14:57:32.8375298-04:00`
26+
`5/01/2008 14:57:32.80 -07:00`
27+
`1 May 2008 2:57:32.8 PM`
28+
`Fri, 15 May 2009 20:10:57 GMT`
29+
2930

3031
Date- and time-based datasets can, in most cases, be described by one or more date/time intervals, such as hourly, daily, monthly, quarterly, and yearly. [!INCLUDE[PRODUCT_NAME](../../includes/ss-mobilereptpub-short.md)] can combine multiple tables of different granularity and display them on a single mobile report. However, keep in mind the relevant intervals from the original dataset(s), as they can help when deciding what date/time filter options to present to the user in the final mobile report.
3132

0 commit comments

Comments
 (0)