Skip to content

Commit 3353a3f

Browse files
rwestMSFTWilliamDAssafMSFT
rwestMSFT
and
WilliamDAssafMSFT
committed
[SCOPED] SQL server -> SQL Server
Apply suggestions from code review Co-authored-by: William Assaf MSFT <74387232+WilliamDAssafMSFT@users.noreply.github.com>
1 parent 0e3218e commit 3353a3f

39 files changed

Lines changed: 49 additions & 48 deletions

File tree

‎docs/big-data-cluster/cluster-monitor-grafana.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.topic: conceptual
1717

1818
This article describes how to monitor an application inside [!INCLUDE[ssbigdataclusters-ss-nover](../includes/ssbigdataclusters-ss-nover.md)]. SQL Server Big Data Clusters expose Grafana Dashboard for monitoring, those metrics are stored in influxDB. Those metrics are categorized as either:
1919
- Kubernetes host-related metrics collected by Telegraf, an agent for collecting, processing, aggregating, and writing metrics.
20-
- Workload-related metrics: those metrics related to SQL Server, Spark and HDFS are collected by CollectD, including such as SQL Server DMV metrics and [SQL server extended events (XEvents)](../relational-databases/extended-events/extended-events.md).
20+
- Workload-related metrics: those metrics related to SQL Server, Spark and HDFS are collected by CollectD, including such as SQL Server DMV metrics and [SQL Server Extended Events (XEvents)](../relational-databases/extended-events/extended-events.md).
2121

2222
> [!IMPORTANT]
2323
> The Internet Explorer browser and older Microsoft Edge browsers are not compatible with Grafana. In Grafana, you will see a black page with errors when using an unsupported browser. Consider the [Chromium-based Microsoft Edge](https://microsoftedgewelcome.microsoft.com/), or review the [supported browsers for Grafana](https://grafana.com/docs/grafana/latest/installation/requirements/#supported-web-browsers).

‎docs/connect/ado-net/introduction-microsoft-data-sqlclient-namespace.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -196,7 +196,7 @@ TLS 1.3 isn't supported by the driver; therefore, it has been removed from the s
196196

197197
### Enable optimized parameter binding
198198

199-
Microsoft.Data.SqlClient introduces a new `SqlCommand` API, `EnableOptimizedParameterBinding` to improve performance of queries with large number of parameters. This property is disabled by default. When set to `true`, parameter names aren't sent to the SQL server when the command is executed.
199+
Microsoft.Data.SqlClient introduces a new `SqlCommand` API, `EnableOptimizedParameterBinding` to improve performance of queries with large number of parameters. This property is disabled by default. When set to `true`, parameter names aren't sent to the [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instance when the command is executed.
200200

201201
```cs
202202
public class SqlCommand

‎docs/connect/jdbc/use-bulk-copy-api-batch-insert-operation.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,8 @@ There are currently these limitations that apply to this feature.
5858
* `IDENTIY_INSERT` isn't managed in the driver. Either don't include identity columns in insert statements, or manually set the `IDENTITY_INSERT` state of your tables between batch insert statements. For more information, see [SET IDENTITY_INSERT](../../t-sql/statements/set-identity-insert-transact-sql.md).
5959
* Because of the limitations of Bulk Copy API, `MONEY`, `SMALLMONEY`, `DATE`, `DATETIME`, `DATETIMEOFFSET`, `SMALLDATETIME`, `TIME`, `GEOMETRY`, and `GEOGRAPHY` data types, are currently not supported for this feature.
6060

61-
If the query fails because of non "SQL server" related errors, the driver logs the error message and falls back to the original logic for batch insert.
61+
If the query fails because of errors unrelated to the [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instance, the driver logs the error message and falls back to the original logic for batch insert.
62+
6263

6364
## Example
6465

‎docs/connect/jdbc/using-ntlm-authentication-to-connect-to-sql-server.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ For more information on connection properties, see [Setting the connection prope
2929

3030
## Remarks
3131

32-
See [Network security: LAN Manager authentication level](/windows/security/threat-protection/security-policy-settings/network-security-lan-manager-authentication-level) for description of the SQL server settings, which control the behavior of NTLM authentication.
32+
See [Network security: LAN Manager authentication level](/windows/security/threat-protection/security-policy-settings/network-security-lan-manager-authentication-level) for description of the [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] settings, which control the behavior of NTLM authentication.
3333

3434
## Logging
3535

‎docs/connect/oledb/features/encryption-and-certificate-validation.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@ The following table describes the encryption and validation outcome for legacy a
116116

117117
## See also
118118

119-
[OLE DB driver for SQL server features](oledb-driver-for-sql-server-features.md)
119+
[OLE DB Driver for SQL Server Features](oledb-driver-for-sql-server-features.md)
120120
[Initialization and authorization properties](../ole-db-data-source-objects/initialization-and-authorization-properties.md)
121121
[Connection string keywords](../applications/using-connection-string-keywords-with-oledb-driver-for-sql-server.md)
122122
[Major version differences](../major-version-differences.md)

‎docs/connect/php/using-always-encrypted-php-drivers.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ $firstName = "Catherine";
111111
$lastName = "Abel;
112112
$birthDate = "1996-10-19";
113113
$params = array($ssn, $firstName, $lastName, $birthDate);
114-
// during sqlsrv_prepare, the driver determines the SQL types for each parameter and pass them to SQL server
114+
// during sqlsrv_prepare, the driver determines the SQL types for each parameter and pass them to SQL Server
115115
$stmt = sqlsrv_prepare($conn, $query, $params);
116116
sqlsrv_execute($stmt);
117117
```
@@ -143,7 +143,7 @@ $ssn = "795-73-9838";
143143
$firstName = "Catherine";
144144
$lastName = "Able";
145145
$birthDate = "1996-10-19";
146-
// during PDO::prepare, the driver determines the SQL types for each parameter and pass them to SQL server
146+
// during PDO::prepare, the driver determines the SQL types for each parameter and pass them to SQL Server
147147
$stmt = $conn->prepare($query);
148148
$stmt->bindParam(1, $ssn);
149149
$stmt->bindParam(2, $firstName);

‎docs/data-quality-services/install-windows/run-dqsinstaller-exe-to-complete-data-quality-server-installation.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ ms.topic: conceptual
6767
|-exportkbs|Export all the knowledge bases to a DQS backup file (.dqsb). You must also specify the full path and file name where you want to export all the knowledge bases.<br /><br /> For more information, see [Export and Import DQS Knowledge Bases Using DQSInstaller.exe](../../data-quality-services/install-windows/export-and-import-dqs-knowledge-bases-using-dqsinstaller-exe.md).|`dqsinstaller.exe -exportkbs <path><filename>`<br /><br /> For example, `dqsinstaller.exe -exportkbs c:\DQSBackup.dqsb`|
6868
|-importkbs|Import all the knowledge bases from a DQS backup file (.dqsb) after completing the [!INCLUDE[ssDQSServer](../../includes/ssdqsserver-md.md)] installation. You must also specify the full path and file name from where you want to import all the knowledge bases.<br /><br /> For more information, see [Export and Import DQS Knowledge Bases Using DQSInstaller.exe](../../data-quality-services/install-windows/export-and-import-dqs-knowledge-bases-using-dqsinstaller-exe.md).|`dqsinstaller.exe -importkbs <path><filename>`<br /><br /> For example, `dqsinstaller.exe -importkbs c:\DQSBackup.dqsb`|
6969
|-upgrade|Upgrades DQS databases schema. You must use this parameter after you have installed a SQL Server update on a previously configured DQS instance. For more information, see [Upgrade DQS Databases Schema After Installing SQL Server Update](../../data-quality-services/install-windows/upgrade-dqs-databases-schema-after-installing-sql-server-update.md).|`dqsinstaller.exe -upgrade`|
70-
|-uninstall|Uninstalls [!INCLUDE[ssDQSServer](../../includes/ssdqsserver-md.md)] from the current SQL Server instance.<br /><br /> You can also export all the knowledge bases in the existing Data Quality Server installation to a DQS backup file (.dqsb), and then uninstall Data Quality Server. For more information, see [Export and Import DQS Knowledge Bases Using DQSInstaller.exe](../../data-quality-services/install-windows/export-and-import-dqs-knowledge-bases-using-dqsinstaller-exe.md).<br /><br /> **\*\* Important \*\*** If you uninstall [!INCLUDE[ssDQSServer](../../includes/ssdqsserver-md.md)] from a SQL server instance using the `-uninstall` command line parameter, all the DQS objects are deleted as part of the uninstall process. You do not have to delete them manually after uninstalling [!INCLUDE[ssDQSServer](../../includes/ssdqsserver-md.md)] as mentioned in [Remove Data Quality Server Objects](../../sql-server/install/remove-data-quality-server-objects.md).|**To just uninstall Data Quality Server:**<br /><br /> `dqsinstaller.exe -uninstall`<br /><br /> **To export all the knowledge bases to a file, and then uninstall Data Quality Server:**<br /><br /> `dqsinstaller.exe -uninstall <path><filename>`<br /><br /> For example, `dqsinstaller.exe -uninstall c:\DQSBackup.dqsb`|
70+
|-uninstall|Uninstalls [!INCLUDE[ssDQSServer](../../includes/ssdqsserver-md.md)] from the current SQL Server instance.<br /><br /> You can also export all the knowledge bases in the existing Data Quality Server installation to a DQS backup file (.dqsb), and then uninstall Data Quality Server. For more information, see [Export and Import DQS Knowledge Bases Using DQSInstaller.exe](../../data-quality-services/install-windows/export-and-import-dqs-knowledge-bases-using-dqsinstaller-exe.md).<br /><br /> **\*\* Important \*\*** If you uninstall [!INCLUDE[ssDQSServer](../../includes/ssdqsserver-md.md)] from a [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instance using the `-uninstall` command line parameter, all the DQS objects are deleted as part of the uninstall process. You do not have to delete them manually after uninstalling [!INCLUDE[ssDQSServer](../../includes/ssdqsserver-md.md)] as mentioned in [Remove Data Quality Server Objects](../../sql-server/install/remove-data-quality-server-objects.md).|**To just uninstall Data Quality Server:**<br /><br /> `dqsinstaller.exe -uninstall`<br /><br /> **To export all the knowledge bases to a file, and then uninstall Data Quality Server:**<br /><br /> `dqsinstaller.exe -uninstall <path><filename>`<br /><br /> For example, `dqsinstaller.exe -uninstall c:\DQSBackup.dqsb`|
7171

7272
**To run DQSInstaller.exe from Command Prompt:**
7373

‎docs/database-engine/configure-windows/buffer-pool-extension.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ ms.topic: conceptual
4343
In [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], A buffer is an 8-KB page in memory, the same size as a data or index page. Thus, the buffer cache is divided into 8-KB pages. A page remains in the buffer cache until the buffer manager needs the buffer area to read in more data. Data is written back to disk only if it is modified. These in-memory modified pages are known as dirty pages. A page is clean when it is equivalent to its database image on disk. Data in the buffer cache can be modified multiple times before being written back to disk.
4444

4545
Buffer pool
46-
Also called buffer cache. The buffer pool is a global resource shared by all databases for their cached data pages. The maximum and minimum size of the buffer pool cache is determined during startup or when the instance of SQL server is dynamically reconfigured by using sp_configure. This size determines the maximum number of pages that can be cached in the buffer pool at any time in the running instance.
46+
Also called buffer cache. The buffer pool is a global resource shared by all databases for their cached data pages. The maximum and minimum size of the buffer pool cache is determined during startup or when the instance of [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] is dynamically reconfigured by using sp_configure. This size determines the maximum number of pages that can be cached in the buffer pool at any time in the running instance.
4747

4848
The maximum memory that can be committed by buffer pool extension can be limited by the other applications running on the machine in case those create significant memory pressure.
4949

‎docs/database-engine/configure-windows/configure-the-network-packet-size-server-configuration-option.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ For more information, see [Server Configuration Options (SQL Server)](../../data
8181

8282
### Configure network packet size on the client side
8383

84-
The following table provides examples of some data connection technologies that you can use to connect to SQL Server and how to control the network packet size when using these in client applications. For a complete list of various data connection technologies that you can use to connect to SQL server visit [Homepage for SQL client programming](../../connect/homepage-sql-connection-programming.md):
84+
The following table provides examples of some data connection technologies that you can use to connect to SQL Server and how to control the network packet size when using these in client applications. For a complete list of various data connection technologies that you can use to connect to [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)], see [Homepage for SQL client programming](../../connect/homepage-sql-connection-programming.md):
8585

8686
| Client library | Option | Default |
8787
| --- | --- | --- |

‎docs/database-engine/install-windows/view-and-read-sql-server-setup-log-files.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,9 +38,9 @@ SQL Server Setup creates log files in a dated and time-stamped folder within **\
3838
![Screenshot showing where to find the ConfigurationFiles.ini file in the Setup Bootstrap folder.](media/view-and-read-sql-server-setup-log-files/setup-bootstrap-example.png)
3939

4040
>[!NOTE]
41-
> The numbers in the path *nnn* correspond to the version of SQL being installed. In the above picture, SQL 2017 was installed, so the folder is 140. For SQL 2016, the folder would be 130, and for SQL 2014 the folder would be 120.
41+
> The numbers in the path *nnn* correspond to the version of [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] being installed. In the above picture, [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] was installed, so the folder is `140`. For [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)], the folder would be `130`, and so on.
4242
43-
SQL server setup completes three basic phases:
43+
[!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] Setup completes three basic phases:
4444

4545
1. Global Rules verification: validates basic system requirements
4646
2. Component update: checks to see if there are any updates available for the media being installed

0 commit comments

Comments
 (0)