Skip to content

Commit f06590a

Browse files
Merge pull request #34325 from rwestMSFT/rw-0605-uuf
Fix UUF items (424036, 430131)
2 parents b8d9137 + d9d458c commit f06590a

File tree

4 files changed

+6
-6
lines changed

4 files changed

+6
-6
lines changed

docs/database-engine/install-windows/validate-a-sql-server-installation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,15 +11,15 @@ helpviewer_keywords:
1111
- "validating installations [SQL Server]"
1212
monikerRange: ">=sql-server-2016"
1313
---
14-
# Validate a SQL Server Installation
14+
# Validate a SQL Server installation
1515

1616
[!INCLUDE [SQL Server -Windows Only](../../includes/applies-to-version/sql-windows-only.md)]
1717

1818
The [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] discovery report can be used to verify the version of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] and the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] features installed on the computer. The **Installed SQL Server features discovery report** displays a report of all products and features installed on the local server, for [!INCLUDE [ssVersion2000](../../includes/ssversion2000-md.md)] and later versions. The [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] features discovery report is available on the **Tools** page on the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Installation center.
1919

2020
## Run SQL Server features discovery report
2121

22-
Launch the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Installation center, using the **Start** menu, point to **All Programs**, point to **Microsoft SQL Server \<Version Name>**, point to **Configuration Tools**, and select **SQL Server Installation Center**. To run the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] features discovery report, select **Tools** in the left-hand navigation area of **SQL Server Installation Center**, and then select **Installed SQL Server features discovery report**.
22+
Launch the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Installation center, using the **Start** menu, point to **All Programs**, point to **Microsoft SQL Server \<Version Name>**, and select **SQL Server Installation Center**. To run the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] features discovery report, select **Tools** in the left-hand navigation area of **SQL Server Installation Center**, and then select **Installed SQL Server features discovery report**.
2323

2424
The [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] discovery report is saved to `%ProgramFiles%\Microsoft SQL Server\<nnn>\Setup Bootstrap\Log\<last Setup Session>`.
2525

docs/integration-services/change-data-capture/the-oracle-cdc-databases.md

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

8080
For the Oracle CDC, the LSN values stored in this table are based on the Oracle System Change Number (SCN) value associated with the change. The first 6 bytes of the LSN value is the original Oracle SCN number.
8181

82-
Also when using the Oracle CDC, the time columns (`tran_begin_time` and `tran_end_time`) store the UTC time of the change rather than the local time as it does with the regular SQL Server CDC. This ensures that daylight savings time changes do not impact the data stored in the lsn_time_mapping.
82+
Also when using the Oracle CDC, the time columns (`tran_begin_time` and `tran_end_time`) store the UTC time of the change rather than the local time as it does with the regular SQL Server CDC. This ensures that daylight saving time changes do not impact the data stored in the lsn_time_mapping.
8383

8484
### cdc.xdbcdc_config
8585

docs/relational-databases/system-catalog-views/sys-time-zone-info-transact-sql.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ monikerRange: "=azure-sqldw-latest || >=sql-server-2016 || >=sql-server-linux-20
2828
| --- | --- | --- |
2929
| `name` | **sysname** | Name of the time zone in Windows standard format. For example, `Cen. Australia Standard Time` or `Central European Standard Time`. |
3030
| `current_utc_offset` | **nvarchar(12)** | Current offset to UTC. For example, `+01:00` or `-07:00`. |
31-
| `is_currently_dst` | **bit** | True if currently observing daylight savings time. |
31+
| `is_currently_dst` | **bit** | True if currently observing daylight saving time. |
3232

3333
## Remarks
3434

docs/t-sql/data-types/datetimeoffset-transact-sql.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -160,9 +160,9 @@ First, verify the time zone name from the [sys.time_zone_info](../../relational-
160160
SELECT * FROM sys.time_zone_info WHERE name = 'Pacific Standard Time';
161161
```
162162

163-
The following example uses the [AT TIME ZONE](../queries/at-time-zone-transact-sql.md) syntax twice. The sample code creates a table `dbo.Audit`, adds data that spans multiple daylight savings time changes, and adds a new **datetimeoffset** column. We assume that the `AuditCreated` column is a ***datetime2** data type without offsets, and was written using the UTC time zone.
163+
The following example uses the [AT TIME ZONE](../queries/at-time-zone-transact-sql.md) syntax twice. The sample code creates a table `dbo.Audit`, adds data that spans multiple daylight saving time changes, and adds a new **datetimeoffset** column. We assume that the `AuditCreated` column is a ***datetime2** data type without offsets, and was written using the UTC time zone.
164164

165-
In the `UPDATE` statement, the `AT TIME ZONE` syntax first adds UTC time zone offset to the existing `AuditCreated` column data, then converts the data from UTC to `Pacific Standard Time`, correctly adjusting the historical data for each past daylight savings time range in the United States.
165+
In the `UPDATE` statement, the `AT TIME ZONE` syntax first adds UTC time zone offset to the existing `AuditCreated` column data, then converts the data from UTC to `Pacific Standard Time`, correctly adjusting the historical data for each past daylight saving time range in the United States.
166166

167167
```sql
168168
CREATE TABLE dbo.Audit (AuditCreated DATETIME2(0) NOT NULL);

0 commit comments

Comments
 (0)