Skip to content

Commit 34dd7dc

Browse files
nschonninschonni
committed
fix: MD038/no-space-in-code
Spaces inside code span elements
1 parent d6ef87a commit 34dd7dc

23 files changed

Lines changed: 32 additions & 32 deletions

‎docs/2014/analysis-services/multidimensional-models/olap-physical/object-naming-rules-analysis-services.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -65,10 +65,10 @@ manager: craigg
6565
|Object|Invalid characters|
6666
|------------|------------------------|
6767
|`Server`|Follow Windows server naming conventions when naming a server object. See [Naming Conventions (Windows)](/windows/desktop/DNS/naming-conventions) for details.|
68-
|`DataSource`|: / \ * &#124; ? " () [] {} <>|
69-
|`Level` or `Attribute`|. , ; ' ` : / \ * &#124; ? " & % $ ! + = [] {} \< >|
70-
|`Dimension` or `Hierarchy`|. , ; ' ` : / \ * &#124; ? " & % $ ! + = () [] {} \<,>|
71-
|All other objects|. , ; ' ` : / \ * &#124; ? " & % $ ! + = () [] {} \< >|
68+
|`DataSource`|`: / \ * | ? " () [] {} <>`|
69+
|`Level` or `Attribute`|```. , ; ' ` : / \ * &| ? " & % $ ! + = [] {} \< >```|
70+
|`Dimension` or `Hierarchy`|```. , ; ' ` : / \ * | ? " & % $ ! + = () [] {} \<,>```|
71+
|All other objects|```. , ; ' ` : / \ * | ? " & % $ ! + = () [] {} \< >```|
7272

7373
**Exceptions: When Reserved Characters are Allowed**
7474

‎docs/2014/reporting-services/tutorial-introducing-expressions.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -692,7 +692,7 @@ manager: kfile
692692
693693
1. From the **Report Builder** button, click **Save As**.
694694
695-
2. Click **Desktop`, `My Documents**, or **My computer**, and then browse to the folder where you want to save the report.
695+
2. Click **Desktop**, **My Documents**, or **My computer**, and then browse to the folder where you want to save the report.
696696
697697
3. In **Name**, replace the default name with **Sales Comparison Summary**.
698698

‎docs/advanced-analytics/data-collection-ml-troubleshooting-process.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ with WITH RESULT SETS (SQL keywords) ((PropertyName nvarchar(100), PropertyValue
117117

118118
If Machine Learning Services is not running, you can determine the installed Python version by looking at the pythonlauncher.config file. We recommend that you make and open a copy of the file so that you don't accidentally change any properties.
119119

120-
1. For SQL Server 2017 only: `C:\Program Files\Microsoft SQL Server\MSSQL14.<instance_name>\MSSQL\Log\ExtensibilityLog\pythonlauncher.config `
120+
1. For SQL Server 2017 only: `C:\Program Files\Microsoft SQL Server\MSSQL14.<instance_name>\MSSQL\Log\ExtensibilityLog\pythonlauncher.config`
121121
2. Get the value for **PYTHONHOME**.
122122
3. Get the value of the current working directory.
123123

@@ -205,7 +205,7 @@ You can get these logs from the following default locations:
205205

206206
* SQL Server 2017
207207

208-
`C:\Program Files\Microsoft SQL Server\MSSQL14.<instance_name>\MSSQL\Log\ExtensibilityLog `
208+
`C:\Program Files\Microsoft SQL Server\MSSQL14.<instance_name>\MSSQL\Log\ExtensibilityLog`
209209

210210
> [!NOTE]
211211
> The exact folder name differs based on the instance name. Depending on your configuration, the folder might be on a different drive.

‎docs/advanced-analytics/install/sql-pretrained-models-install.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ The install paths for R and Python models are as follows:
4747

4848
+ For R: `C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\R_SERVICES\library\MicrosoftML\mxLibs\x64`
4949

50-
+ For Python: `C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\PYTHON_SERVICES\Lib\site-packages\microsoftml\mxLibs `
50+
+ For Python: `C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\PYTHON_SERVICES\Lib\site-packages\microsoftml\mxLibs`
5151

5252
Model file names are listed below:
5353

‎docs/analysis-services/data-mining/microsoft-logistic-regression-algorithm-technical-reference.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,9 +37,9 @@ manager: kfile
3737

3838
**Continuous values**
3939

40-
Value is present: `(X - μ)/σ ` (X is the actual value being encoded)
40+
Value is present: `(X - μ)/σ` (X is the actual value being encoded)
4141

42-
Value is absent: `- μ/σ ` (negative mu divided by sigma)
42+
Value is absent: `- μ/σ` (negative mu divided by sigma)
4343

4444
**Discrete values**
4545

‎docs/analytics-platform-system/transparent-data-encryption.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -233,15 +233,15 @@ If a DMK exists on the appliance on which Upgrade or Replace VM was performed, D
233233

234234
Example of the upgrade action. Replace `**********` with your DMK password.
235235

236-
`setup.exe /Action=ProvisionUpgrade ... DMKPassword='**********' `
236+
`setup.exe /Action=ProvisionUpgrade ... DMKPassword='**********'`
237237

238238
Example of the action to replace a virtual machine.
239239

240-
`setup.exe /Action=ReplaceVM ... DMKPassword='**********' `
240+
`setup.exe /Action=ReplaceVM ... DMKPassword='**********'`
241241

242242
During upgrade, if a user DB is encrypted and the DMK password is not provided, the upgrade action will fail. During replace, if the correct password is not provided when a DMK exists, the operation will skip the DMK recovery step. All the other steps will be completed at the end of the replace VM action, however the action will report failure at the end to indicate that additional steps are required. In the setup logs (located in **\ProgramData\Microsoft\Microsoft SQL Server Parallel Data Warehouse\100\Logs\Setup\\<time-stamp>\Detail-Setup**), the following warning will be shown near the end.
243243

244-
`*** WARNING \*\*\* DMK is detected in master database, but could not be recovered automatically! The DMK password was either not provided or is incorrect! `
244+
`*** WARNING \*\*\* DMK is detected in master database, but could not be recovered automatically! The DMK password was either not provided or is incorrect!`
245245

246246
Execute these statement manually in PDW and restart appliance after that in order to recover DMK:
247247

‎docs/big-data-cluster/train-and-create-machinelearning-models-with-spark.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ data = data_all.select(select_cols)
8484

8585
## Step 4 - Split as training and test set
8686

87-
Use 75% of rows to train the model and rest of the 25% to evaluate the model. Additionally, persist the train and test data sets to HDFS storage. The step is not necessary,but shown to demonstrate saving and loading with ORC format. Other formats, for example, `Parquet `may also be used.
87+
Use 75% of rows to train the model and rest of the 25% to evaluate the model. Additionally, persist the train and test data sets to HDFS storage. The step is not necessary,but shown to demonstrate saving and loading with ORC format. Other formats, for example, `Parquet` may also be used.
8888

8989
Post this step you should see two directories created with the name AdultCensusIncomeTrain and AdultCensusIncomeTest
9090

‎docs/connect/jdbc/jdbc-4-3-compliance-for-the-jdbc-driver.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,5 +25,5 @@ With Microsoft JDBC Driver 7.0 for SQL Server release, the driver is now JAVA 10
2525

2626
|New API|Description|Noteworthy Implementation|
2727
|-----------------|-----------------|-------------------------------|
28-
|void java.sql.connection.beginRequest()|Hints to the driver that a request, an independent unit of work, is beginning on this connection. For more details, see [java.sql.Connection](https://docs.oracle.com/javase/9/docs/api/java/sql/Connection.html#beginRequest--).|Saves the values of the connection fields that are modifiable through public API methods: `databaseAutoCommitMode`, `transactionIsolationLevel`, `networkTimeout`, `holdability`, `sendTimeAsDatetime`, `statementPoolingCacheSize`, `disableStatementPooling`, `serverPreparedStatementDiscardThreshold`, `enablePrepareOnFirstPreparedStatementCall `, `catalogName`, `sqlWarnings`, `useBulkCopyForBatchInsert `.|
28+
|void java.sql.connection.beginRequest()|Hints to the driver that a request, an independent unit of work, is beginning on this connection. For more details, see [java.sql.Connection](https://docs.oracle.com/javase/9/docs/api/java/sql/Connection.html#beginRequest--).|Saves the values of the connection fields that are modifiable through public API methods: `databaseAutoCommitMode`, `transactionIsolationLevel`, `networkTimeout`, `holdability`, `sendTimeAsDatetime`, `statementPoolingCacheSize`, `disableStatementPooling`, `serverPreparedStatementDiscardThreshold`, `enablePrepareOnFirstPreparedStatementCall`, `catalogName`, `sqlWarnings`, `useBulkCopyForBatchInsert`.|
2929
|void java.sql.connection.endRequest()|Hints to the driver that a request, an independent unit of work, has completed. For more details, see [java.sql.Connection](https://docs.oracle.com/javase/9/docs/api/java/sql/Connection.html#endRequest--).|Closes the statements that are created during the work unit and rolls back any open transactions. The method also reverts the changes to the connection fields that are listed above.|

‎docs/connect/odbc/linux-mac/connecting-with-sqlcmd.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ In the current release, the following options are available:
4040

4141
- -C Trust server certificate.
4242

43-
- -d *database_name* Issue a `USE `*database_name* statement when you start `sqlcmd`.
43+
- -d *database_name* Issue a `USE` *database_name* statement when you start `sqlcmd`.
4444

4545
- -D Causes the value passed to the `sqlcmd` -S option to be interpreted as a data source name (DSN). For more information, see "DSN Support in `sqlcmd` and `bcp`" at the end of this topic.
4646

‎docs/database-engine/configure-windows/database-engine-service-startup-options.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ manager: craigg
5959
|**-g** *memory_to_reserve*|Specifies an integer number of megabytes (MB) of memory that [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] will leave available for memory allocations within the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] process, but outside the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] memory pool set by [max_server_memory](../../database-engine/configure-windows/server-memory-server-configuration-options.md) server setting. The memory outside of the memory pool is the area used by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] for loading items, such as extended procedure .dll files, the OLE DB providers referenced by distributed queries, and automation objects referenced in [!INCLUDE[tsql](../../includes/tsql-md.md)] statements. The default is 256 MB.<br /><br /> Use of this option might help tune memory allocation, but only when physical memory exceeds the configured limit set by the operating system on virtual memory available to applications. Use of this option might be appropriate in large memory configurations in which the memory usage requirements of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] are atypical and the virtual address space of the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] process is totally in use. Incorrect use of this option can lead to conditions under which an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] may not start or may encounter run-time errors.<br /><br /> Use the default for the **-g** parameter unless you see any of the following warnings in the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] error log:<br /> "Failed Virtual Allocate Bytes: FAIL_VIRTUAL_RESERVE \<size>"<br /> "Failed Virtual Allocate Bytes: FAIL_VIRTUAL_COMMIT \<size>"<br /><br /> These messages might indicate that [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is trying to free parts of the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] memory pool in order to find space for items, such as extended stored procedure .dll files or automation objects. In this case, consider increasing the amount of memory reserved by the **-g** switch.<br /><br /> Using a value lower than the default will increase the amount of memory available to the memory pool managed by the SQL Server Memory Manager and thread stacks; this may, in turn, provide some performance benefit to memory-intensive workloads in systems that do not use many extended stored procedures, distributed queries, or automation objects.|
6060
|**-kDecimalNumber**| This startup parameter limits the number of checkpoint I/O requests per second, where the **DecimalNumber** represents the checkpoint speed in MB per second. Changing this value can impact the speed of taking backups, or going through the recovery process so proceed with caution. For more information about this startup parameter, please see hot fix where the [-k parameter](https://support.microsoft.com/en-us/help/929240/fix-i-o-requests-that-are-generated-by-the-checkpoint-process-may-caus) was introduced.|
6161
|**-m**|Starts an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] in single-user mode. When you start an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] in single-user mode, only a single user can connect, and the CHECKPOINT process is not started. CHECKPOINT guarantees that completed transactions are regularly written from the disk cache to the database device. (Typically, this option is used if you experience problems with system databases that should be repaired.) Enables the sp_configure allow updates option. By default, allow updates is disabled. Starting [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] in single-user mode enables any member of the computer's local Administrators group to connect to the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] as a member of the sysadmin fixed server role. For more information, see [Connect to SQL Server When System Administrators Are Locked Out](../../database-engine/configure-windows/connect-to-sql-server-when-system-administrators-are-locked-out.md). For more information about single-user mode, see [Start SQL Server in Single-User Mode](../../database-engine/configure-windows/start-sql-server-in-single-user-mode.md).|
62-
|**-mClient Application Name**|Limits the connections to a specified client application. For example, `-mSQLCMD` limits connections to a single connection and that connection must identify itself as the SQLCMD client program. Use this option when you are starting [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] in single-user mode and an unknown client application is taking the only available connection. Use `"Microsoft SQL Server Management Studio - Query" ` to connect with the SSMS Query Editor. The SSMS Query Editor option cannot be configured by using [!INCLUDE[ssNoVersion_md](../../includes/ssnoversion-md.md)] Configuration Manager because it includes the dash character which is rejected by the tool.<br /><br /> Client Application Name is case sensitive. Double quotes are required if the application name contains spaces or special characters.<br /><br />**Examples when starting from the command line:**<br /><br />`C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\sqlservr -s MSSQLSERVER -m"Microsoft SQL Server Management Studio - Query"` <br /><br />`C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\sqlservr -s MSSQLSERVER -mSQLCMD` <br /><br /> **Security Note:** Do not use this option as a security feature. The client application provides the client application name, and can provide a false name as part of the connection string.|
62+
|**-mClient Application Name**|Limits the connections to a specified client application. For example, `-mSQLCMD` limits connections to a single connection and that connection must identify itself as the SQLCMD client program. Use this option when you are starting [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] in single-user mode and an unknown client application is taking the only available connection. Use `"Microsoft SQL Server Management Studio - Query"` to connect with the SSMS Query Editor. The SSMS Query Editor option cannot be configured by using [!INCLUDE[ssNoVersion_md](../../includes/ssnoversion-md.md)] Configuration Manager because it includes the dash character which is rejected by the tool.<br /><br /> Client Application Name is case sensitive. Double quotes are required if the application name contains spaces or special characters.<br /><br />**Examples when starting from the command line:**<br /><br />`C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\sqlservr -s MSSQLSERVER -m"Microsoft SQL Server Management Studio - Query"` <br /><br />`C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\sqlservr -s MSSQLSERVER -mSQLCMD` <br /><br /> **Security Note:** Do not use this option as a security feature. The client application provides the client application name, and can provide a false name as part of the connection string.|
6363
|**-n**|Does not use the Windows application log to record [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] events. If you start an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] with **-n**, we recommend that you also use the **-e** startup option. Otherwise, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] events are not logged.|
6464
|**-s**|Allows you to start a named instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Without the **-s** parameter set, the default instance will try to start. You must switch to the appropriate BINN directory for the instance at a command prompt before starting **sqlservr.exe**. For example, if Instance1 were to use `\mssql$Instance1` for its binaries, the user must be in the `\mssql$Instance1\binn` directory to start **sqlservr.exe -s instance1**.|
6565
|**-T** *trace#*|Indicates that an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] should be started with a specified trace flag (*trace#*) in effect. Trace flags are used to start the server with nonstandard behavior. For more information, see [Trace Flags &#40;Transact-SQL&#41;](../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md).<br /><br /> **Important:** When specifying a trace flag with the **-T** option, use an uppercase "T" to pass the trace flag number. A lowercase "t" is accepted by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], but this sets other internal trace flags that are required only by [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] support engineers. (Parameters specified in the Control Panel startup window are not read.)|

0 commit comments

Comments
 (0)