Skip to content

Commit 5a68acd

Browse files
SaisangSaisang
committed
manual fix multiple asterisks
1 parent 6cecdf3 commit 5a68acd

26 files changed

Lines changed: 54 additions & 54 deletions

File tree

‎docs/2014/sql-server/install/user-defined-functions-are-not-allowed-in-system-function-schema.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ manager: craigg
4949

5050
4. Replace references to **system_function_schema** with **dbo** in all scripts that contain user-defined function DDL statements.
5151

52-
5. Modify scripts that invoke these functions to use either the two-part name dbo**.***function_name*, or the three-part name *database_name***.**dbo.*function_name*.
52+
5. Modify scripts that invoke these functions to use either the two-part name dbo**.**_function_name_, or the three-part name _database_name_**.**dbo.*function_name*.
5353

5454
For more information, see the following topics in SQL Server Books Online:
5555

‎docs/ado/guide/appendixes/visual-c-ado-programming.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ objectPtr->PutProperty(value);      // set property value
5959
variable = objectPtr->GetProperty;  // get property value
6060
```
6161
62-
The compiler will generate the appropriate **Get***-*, **Put**-, or **PutRef**_Property_ call based on what alternative syntax is declared and whether the property is being read or written.
62+
The compiler will generate the appropriate **Get**-, **Put**-, or **PutRef**_Property_ call based on what alternative syntax is declared and whether the property is being read or written.
6363
6464
The **__declspec(property...)** compiler directive can only declare **get**, **put**, or **get** and **put** alternative syntax for a function. Read-only operations only have a **get** declaration; write-only operations only have a **put** declaration; operations that are both read and write have both **get** and **put** declarations.
6565

‎docs/ado/guide/data/types-of-events.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,15 +22,15 @@ manager: craigg
2222
There are two basic types of events. "Will Events," which are called before an operation starts, usually include "Will" in their names - for example, **WillChangeRecordset** or **WillConnect**. Events that are called after an event has been completed usually include "Complete" in their names - for example, **RecordChangeComplete** or **ConnectComplete**. Exceptions exist - such as **InfoMessage** - but these occur after the associated operation has completed.
2323

2424
## Will Events
25-
Event handlers called before the operation starts offer you the opportunity to examine or modify the operation parameters, and then either cancel the operation or allow it to complete. These event-handler routines usually have names of the form **Will_Event_**.
25+
Event handlers called before the operation starts offer you the opportunity to examine or modify the operation parameters, and then either cancel the operation or allow it to complete. These event-handler routines usually have names of the form <strong>Will*Event*</strong>.
2626

2727
## Complete Events
28-
Event handlers called after an operation completes can notify your application that an operation has concluded. Such an event handler is also notified when a Will event handler cancels a pending operation. These event-handler routines usually have names of the form **_Event_Complete**.
28+
Event handlers called after an operation completes can notify your application that an operation has concluded. Such an event handler is also notified when a Will event handler cancels a pending operation. These event-handler routines usually have names of the form <strong>*Event*Complete</strong>.
2929

3030
Will and Complete events are typically used in pairs.
3131

3232
## Other Events
33-
The other event handlers - that is, events whose names are not of the form **Will*Event**_ or _**Event*Complete** - are called only after an operation completes. These events are **Disconnect**, **EndOfRecordset**, and **InfoMessage**.
33+
The other event handlers - that is, events whose names are not of the form <strong>Will*Event*</strong> or <strong>*Event*Complete</strong> - are called only after an operation completes. These events are **Disconnect**, **EndOfRecordset**, and **InfoMessage**.
3434

3535
## See Also
3636
[ADO Event Handler Summary](../../../ado/guide/data/ado-event-handler-summary.md)

‎docs/analytics-platform-system/uninstall-analytics-platform-system-hotfixes.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,13 +21,13 @@ To perform these steps, you will need:
2121

2222
- An Analytics Platform System login with permissions to access the Admin Console to monitor the appliance.
2323

24-
- The Domain Administrator account to login to the *<appliance_domain>***-HST01** node.
24+
- The Domain Administrator account to login to the <em><appliance_domain></em>**-HST01** node.
2525

2626
- The Knowledge Base article number for the hotfix to uninstall.
2727

2828
## <a name="HowToUninstallPDW"></a>To uninstall a SQL Server PDW hotfix
2929

30-
1. Log on to the *<appliance_domain>***-HST01** node as the Fabric Domain Administrator.
30+
1. Log on to the <em><appliance_domain></em>**-HST01** node as the Fabric Domain Administrator.
3131

3232
2. Use the Run as Administrator option to open a Command Prompt.
3333

‎docs/analytics-platform-system/uninstall-microsoft-updates.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,11 +21,11 @@ To perform these steps, you will need:
2121

2222
- An Analytics Platform System login with permissions to access the Admin Console to monitor the appliance.
2323

24-
- Knowledge of the Fabric Domain Administrator account to log in to the *<Fabric Domain>***-HST01** node.
24+
- Knowledge of the Fabric Domain Administrator account to log in to the <em><Fabric Domain></em>**-HST01** node.
2525

2626
## <a name="HowToUninstallMSFT"></a>To uninstall Microsoft updates
2727

28-
1. Log in to the *<Fabric Domain>***-HST01** node as the Fabric Domain Administrator.
28+
1. Log in to the <em><Fabric Domain></em>**-HST01** node as the Fabric Domain Administrator.
2929

3030
2. To uninstall all updates that are approved for WSUS to uninstall, open a Command Prompt window and enter the following command. Replace the placeholder items *< >* with the appropriate information.
3131

‎docs/database-engine/availability-groups/windows/use-the-fail-over-availability-group-wizard-sql-server-management-studio.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,7 @@ manager: craigg
145145
|Value|Description|
146146
|-----------|-----------------|
147147
|**No data loss**|This secondary replica currently supports planned failover. This value occurs only when a synchronous-commit mode secondary replica is currently synchronized with the primary replica.|
148-
|**Data loss, Warnings(** *#* **)**|This secondary replica currently supports forced failover (with possible data loss). This value occurs whenever the secondary replica is not synchronized with the primary replica. Click the data-loss warnings link for information about the possible data loss.|
148+
|**Data loss, Warnings(** _#_ **)**|This secondary replica currently supports forced failover (with possible data loss). This value occurs whenever the secondary replica is not synchronized with the primary replica. Click the data-loss warnings link for information about the possible data loss.|
149149

150150
**Refresh**
151151
Click to update the grid.

‎docs/odbc/reference/develop-app/update-delete-and-insert-statements.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -23,19 +23,19 @@ SQL-based applications make changes to tables by executing the **UPDATE**, **DEL
2323

2424
The syntax of these statements is:
2525

26-
**UPDATE** *table-name*
26+
**UPDATE** _table-name_
2727

28-
**SET** *column-identifier* **=** {*expression* &#124; **NULL**}
28+
**SET** _column-identifier_ **=** {*expression* &#124; **NULL**}
2929

30-
[**,** *column-identifier* **=** {*expression* &#124; **NULL**}]...
30+
[**,** _column-identifier_ **=** {*expression* &#124; **NULL**}]...
3131

32-
[**WHERE** *search-condition*]
32+
[**WHERE** _search-condition_]
3333

34-
**DELETE FROM** *table-name*[**WHERE** *search-condition*]
34+
**DELETE FROM** _table-name_[**WHERE** _search-condition_]
3535

36-
**INSERT INTO** *table-name*[**(***column-identifier* [**,** *column-identifier*]...**)**]
36+
**INSERT INTO** _table-name_[**(** _column-identifier_ [**,** _column-identifier_]...**)**]
3737

38-
{*query-specification* &#124; **VALUES (***insert-value* [**,** *insert-value*]...**)**}
38+
{*query-specification* &#124; **VALUES (** _insert-value_ [**,** _insert-value_]...**)**}
3939

4040
Note that the *query-specification* element is valid only in the Core and Extended SQL grammars, and that the *expression* and *search-condition* elements become more complex in the Core and Extended SQL grammars.
4141

‎docs/relational-databases/collations/write-international-transact-sql-statements.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,9 +34,9 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
3434

3535
**{ ts'**yyyy**-**_mm_**-_**dd**hh_**:**_mm_**:**_ss_[**.**_fff_] **'}** such as: **{ ts'**1998**-**09**-**24 10**:**02**:**20**' }**
3636

37-
**{ d'** *yyyy* **-** *mm* **-** *dd* **'}** such as: **{ d'**1998**-**09**-**24**'}**
37+
**{ d'** _yyyy_ **-** _mm_ **-** _dd_ **'}** such as: **{ d'**1998**-**09**-**24**'}**
3838

39-
**{ t'** *hh* **:** *mm* **:** *ss* **'}** such as: **{ t'**10:02:20**'}**
39+
**{ t'** _hh_ **:** _mm_ **:** _ss_ **'}** such as: **{ t'**10:02:20**'}**
4040

4141
- Applications that use other APIs, or [!INCLUDE[tsql](../../includes/tsql-md.md)] scripts, stored procedures, and triggers, should use the unseparated numeric strings. For example, *yyyymmdd* as 19980924.
4242

‎docs/relational-databases/databases/value-for-extended-property-dialog-box.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
2020
---
2121
# Value for Extended Property Dialog Box
2222
[!INCLUDE[appliesto-ss-asdb-xxxx-xxx-md](../../includes/appliesto-ss-asdb-xxxx-xxx-md.md)]
23-
Use the **Value for** *\<property name>* dialog box to enter or view a value. This is a common dialog box that can be opened from several locations.
23+
Use the **Value for** _\<property name>_ dialog box to enter or view a value. This is a common dialog box that can be opened from several locations.
2424

2525
## UIElement List
2626
**Extended property name**

‎docs/relational-databases/in-memory-oltp/unsupported-sql-server-features-for-in-memory-oltp.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,8 +58,8 @@ With a few exceptions, cross-database transactions are not supported. The follow
5858

5959
- Keyset and dynamic cursors on queries accessing memory-optimized tables. These cursors are degraded to static and read-only.
6060

61-
- Using **MERGE INTO** *target*, where *target* is a memory-optimized table, is unsupported.
62-
- **MERGE USING** *source* is supported for memory-optimized tables.
61+
- Using **MERGE INTO** _target_, where *target* is a memory-optimized table, is unsupported.
62+
- **MERGE USING** _source_ is supported for memory-optimized tables.
6363

6464
- The ROWVERSION (TIMESTAMP) data type is not supported. For more information, see [FROM &#40;Transact-SQL&#41;](../../t-sql/queries/from-transact-sql.md).
6565

0 commit comments

Comments
 (0)