Skip to content

Commit 346e661

Browse files
authored
Merge pull request #19538 from MicrosoftDocs/FromPublicRepo
Confirm merge from FromPublicRepo to master to sync with https://github.com/MicrosoftDocs/sql-docs (branch live)
2 parents af22967 + 951227e commit 346e661

File tree

4 files changed

+112
-106
lines changed

4 files changed

+112
-106
lines changed

docs/master-data-services/microsoft-excel-add-in/master-data-services-add-in-for-microsoft-excel.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,9 @@ ms.author: lle
2626
>* Download the Master Data Services Add-in for Excel for SQL Server 2016 SP2 from [this Microsoft Download Center page](https://www.microsoft.com/download/details.aspx?id=56838).
2727
>* Download the [!INCLUDE[ssMDSshort](../../includes/ssmdsshort-md.md)] [!INCLUDE[ssMDSXLS](../../includes/ssmdsxls-md.md)] for SQL Server 2017 from [this Microsoft Download Center page](https://go.microsoft.com/fwlink/?linkid=836867).
2828
>* Download the Master Data Services Add-in for Excel for SQL Server 2019 CTP from [this Microsoft Download Center page](https://go.microsoft.com/fwlink/?linkid=2086948).
29-
29+
30+
> [!NOTE]
31+
> The Master Data Services Add-in for Excel requires the Office Automation Security level to be set to 1 (Macros enabled), the default, or 2 (Use application macro security level).
3032
3133
## Terms
3234
When working with the Add-in, you may encounter the following terms. For more information about these concepts, see [Master Data Services Overview (MDS)](../../master-data-services/master-data-services-overview-mds.md).
Lines changed: 102 additions & 102 deletions
Original file line numberDiff line numberDiff line change
@@ -1,102 +1,102 @@
1-
---
2-
description: "View or Change Registered Filters and Word Breakers"
3-
title: "View or change registered filters & word breakers"
4-
ms.date: "03/14/2017"
5-
ms.prod: sql
6-
ms.prod_service: "search, sql-database"
7-
ms.technology: search
8-
ms.topic: conceptual
9-
helpviewer_keywords:
10-
- "full-text search [SQL Server], word breakers"
11-
- "full-text search [SQL Server], filters"
12-
- "filters [full-text search]"
13-
- "word breakers [full-text search]"
14-
ms.assetid: f88c54df-b1aa-4701-807f-dc92c32363fd
15-
author: pmasl
16-
ms.author: pelopes
17-
ms.reviewer: mikeray
18-
monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current"
19-
ms.custom: "seo-lt-2019"
20-
---
21-
# View or Change Registered Filters and Word Breakers
22-
[!INCLUDE [SQL Server Azure SQL Database](../../includes/applies-to-version/sql-asdb.md)]
23-
After any word breakers or filters are installed or uninstalled on a system, the changes do not automatically take effect on server instances. This topic describes how to view the currently registered word breaker or filters and how to register newly installed word breakers and filters on an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
24-
25-
### To view a list of languages whose word breakers are currently registered
26-
27-
1. Use the [sys.fulltext_languages](../../relational-databases/system-catalog-views/sys-fulltext-languages-transact-sql.md) catalog view, as follows:
28-
29-
```
30-
SELECT * FROM sys.fulltext_languages;
31-
```
32-
33-
### To view a list of the filters that are currently registered
34-
35-
1. Use the [sp_help_fulltext_system_components](../../relational-databases/system-stored-procedures/sp-help-fulltext-system-components-transact-sql.md) system stored procedure, as follows:
36-
37-
```
38-
EXEC sp_help_fulltext_system_components 'filter';
39-
```
40-
41-
### To register newly installed word breakers and filters
42-
43-
1. Use the [sp_fulltext_service](../../relational-databases/system-stored-procedures/sp-fulltext-service-transact-sql.md) system stored procedure to update the list of languages, as follows:
44-
45-
```
46-
exec sp_fulltext_service 'update_languages';
47-
```
48-
49-
### To unregister uninstalled word breakers and filters
50-
51-
1. Use the **sp_fulltext_service** to update the list of languages, as follows:
52-
53-
```
54-
exec sp_fulltext_service 'update_languages'
55-
```
56-
57-
2. Use the **sp_fulltext_service** to restart the filter daemon host processes (fdhost.exe), as follows:
58-
59-
```
60-
exec sp_fulltext_service 'restart_all_fdhosts';
61-
```
62-
63-
### To replace existing word breakers or filters when installing new ones
64-
65-
1. When preparing to install a DLL file that contains new word breakers or filters, verify that it has a different filename from any of the existing DLL files installed on your server instance.
66-
67-
2. Copy the new DLL file into the directory containing the standard [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] DLL files for the server instance. The default location is:
68-
69-
C:\Program Files\Microsoft SQL Server\MSSQL.*instance_name*\MSSQL\Binn
70-
71-
> [!IMPORTANT]
72-
> We highly recommend that you load only signed and verified components. Also, we recommend that you run the FDHOST Launcher (MSSQLFDLauncher) Service with the least possible privileges.
73-
74-
3. Install the new word breaker or filters.
75-
76-
**To install and load Microsoft Filter Pack IFilters**
77-
78-
- [How to register Microsoft Filter Pack IFilters with SQL Server]()
79-
80-
4. Use **sp_fulltext_service** to load newly installed word breakers and filters in the server instance, as follows:
81-
82-
```
83-
EXEC sp_fulltext_service @action='load_os_resources', @value=1;
84-
```
85-
86-
5. Use **sp_fulltext_service** to update the list of languages, as follows:
87-
88-
```
89-
EXEC sp_fulltext_service 'update_languages';
90-
```
91-
92-
6. Restart the filter daemon host processes (fdhost.exe), using **sp_fulltext_service** as follows:
93-
94-
```
95-
EXEC sp_fulltext_service 'restart_all_fdhosts';
96-
```
97-
98-
## See Also
99-
[Set the Service Account for the Full-text Filter Daemon Launcher](../../relational-databases/search/set-the-service-account-for-the-full-text-filter-daemon-launcher.md)
100-
[Configure and Manage Filters for Search](../../relational-databases/search/configure-and-manage-filters-for-search.md)
101-
[Configure and Manage Word Breakers and Stemmers for Search](../../relational-databases/search/configure-and-manage-word-breakers-and-stemmers-for-search.md)
102-
1+
---
2+
description: "View or Change Registered Filters and Word Breakers"
3+
title: "View or change registered filters & word breakers"
4+
ms.date: "03/14/2017"
5+
ms.prod: sql
6+
ms.prod_service: "search, sql-database"
7+
ms.technology: search
8+
ms.topic: conceptual
9+
helpviewer_keywords:
10+
- "full-text search [SQL Server], word breakers"
11+
- "full-text search [SQL Server], filters"
12+
- "filters [full-text search]"
13+
- "word breakers [full-text search]"
14+
ms.assetid: f88c54df-b1aa-4701-807f-dc92c32363fd
15+
author: pmasl
16+
ms.author: pelopes
17+
ms.reviewer: mikeray
18+
monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current"
19+
ms.custom: "seo-lt-2019"
20+
---
21+
# View or Change Registered Filters and Word Breakers
22+
[!INCLUDE [SQL Server Azure SQL Database](../../includes/applies-to-version/sql-asdb.md)]
23+
After any word breakers or filters are installed or uninstalled on a system, the changes do not automatically take effect on server instances. This topic describes how to view the currently registered word breaker or filters and how to register newly installed word breakers and filters on an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
24+
25+
### To view a list of languages whose word breakers are currently registered
26+
27+
1. Use the [sys.fulltext_languages](../../relational-databases/system-catalog-views/sys-fulltext-languages-transact-sql.md) catalog view, as follows:
28+
29+
```
30+
SELECT * FROM sys.fulltext_languages;
31+
```
32+
33+
### To view a list of the filters that are currently registered
34+
35+
1. Use the [sp_help_fulltext_system_components](../../relational-databases/system-stored-procedures/sp-help-fulltext-system-components-transact-sql.md) system stored procedure, as follows:
36+
37+
```
38+
EXEC sp_help_fulltext_system_components 'filter';
39+
```
40+
41+
### To register newly installed word breakers and filters
42+
43+
1. Use the [sp_fulltext_service](../../relational-databases/system-stored-procedures/sp-fulltext-service-transact-sql.md) system stored procedure to update the list of languages, as follows:
44+
45+
```
46+
EXEC sp_fulltext_service 'update_languages';
47+
```
48+
49+
### To unregister uninstalled word breakers and filters
50+
51+
1. Use the **sp_fulltext_service** to update the list of languages, as follows:
52+
53+
```
54+
EXEC sp_fulltext_service 'update_languages';
55+
```
56+
57+
2. Use the **sp_fulltext_service** to restart the filter daemon host processes (fdhost.exe), as follows:
58+
59+
```
60+
EXEC sp_fulltext_service 'restart_all_fdhosts';
61+
```
62+
63+
### To replace existing word breakers or filters when installing new ones
64+
65+
1. When preparing to install a DLL file that contains new word breakers or filters, verify that it has a different filename from any of the existing DLL files installed on your server instance.
66+
67+
2. Copy the new DLL file into the directory containing the standard [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] DLL files for the server instance. The default location is:
68+
69+
C:\Program Files\Microsoft SQL Server\MSSQL.*instance_name*\MSSQL\Binn
70+
71+
> [!IMPORTANT]
72+
> We highly recommend that you load only signed and verified components. Also, we recommend that you run the FDHOST Launcher (MSSQLFDLauncher) Service with the least possible privileges.
73+
74+
3. Install the new word breaker or filters.
75+
76+
**To install and load Microsoft Filter Pack IFilters**
77+
78+
- [How to register Microsoft Filter Pack IFilters with SQL Server]()
79+
80+
4. Use **sp_fulltext_service** to load newly installed word breakers and filters in the server instance, as follows:
81+
82+
```
83+
EXEC sp_fulltext_service @action='load_os_resources', @value=1;
84+
```
85+
86+
5. Use **sp_fulltext_service** to update the list of languages, as follows:
87+
88+
```
89+
EXEC sp_fulltext_service 'update_languages';
90+
```
91+
92+
6. Restart the filter daemon host processes (fdhost.exe), using **sp_fulltext_service** as follows:
93+
94+
```
95+
EXEC sp_fulltext_service 'restart_all_fdhosts';
96+
```
97+
98+
## See Also
99+
[Set the Service Account for the Full-text Filter Daemon Launcher](../../relational-databases/search/set-the-service-account-for-the-full-text-filter-daemon-launcher.md)
100+
[Configure and Manage Filters for Search](../../relational-databases/search/configure-and-manage-filters-for-search.md)
101+
[Configure and Manage Word Breakers and Stemmers for Search](../../relational-databases/search/configure-and-manage-word-breakers-and-stemmers-for-search.md)
102+

docs/t-sql/database-console-commands/dbcc-checktable-transact-sql.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -174,7 +174,11 @@ By default, DBCC CHECKTABLE performs parallel checking of objects. The degree of
174174
Parallel checking can be disabled by using trace flag 2528. For more information, see [Trace Flags (Transact-SQL)](../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md).
175175

176176
> [!NOTE]
177-
> During a DBCC CHECKTABLE operation, the bytes that are stored in a byte-ordered user-defined type column must be equal to the computed serialization of the user-defined type value. If this is not true, the DBCC CHECKTABLE routine will report a consistency error.
177+
> During a DBCC CHECKTABLE operation, the bytes that are stored in a byte-ordered user-defined type column must be equal to the computed serialization of the user-defined type value. If this is not true, the DBCC CHECKTABLE routine will report a consistency error.
178+
179+
> [!NOTE]
180+
> This feature is not available in every edition of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. For more information, see parallel consistency check in the RDBMS Manageability section of [Features Supported by the Editions of SQL Server](../../sql-server/editions-and-components-of-sql-server-version-15.md#RDBMSM).
181+
178182

179183
## Understanding DBCC Error Messages
180184
After the DBCC CHECKTABLE command finishes, a message is written to the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] error log. If the DBCC command successfully executes, the message indicates a successful completion and the amount of time that the command ran. If the DBCC command stops before completing the check because of an error, the message indicates the command was terminated, a state value, and the amount of time the command ran. The following table lists and describes the state values that can be included in the message.

docs/t-sql/statements/create-index-transact-sql.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,7 @@ CREATE [ UNIQUE ] [ CLUSTERED | NONCLUSTERED ] INDEX index_name
138138
}
139139
140140
<filter_predicate> ::=
141-
<conjunct> [ AND <conjunct> ]
141+
<conjunct> [ AND ] [ ...n ]
142142
143143
<conjunct> ::=
144144
<disjunct> | <comparison>
@@ -486,7 +486,7 @@ Indexes, including indexes on global temp tables, can be created online except f
486486
- Disabled clustered indexes
487487
- Columnstore indexes
488488
- Clustered index, if the underlying table contains LOB data types (**image**, **ntext**, **text**) and spatial data types
489-
- **varchar(max)** and **varbinary(max)** columns cannot be part of an index. In [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] (Starting with [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)]) and [!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)], when a table contains **varchar(max)** or **varbinary(max)** columns, a clustered index containing other columns can be built or rebuilt using the **ONLINE** option. [!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)] does not permit the **ONLINE** option when the base table contains **varchar(max)** or **varbinary(max)** columns
489+
- **varchar(max)** and **varbinary(max)** columns cannot be part of an index key. In [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] (Starting with [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)]) and [!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)], when a table contains **varchar(max)** or **varbinary(max)** columns, a clustered index containing other columns can be built or rebuilt using the **ONLINE** option.
490490

491491
For more information, see [How Online Index Operations Work](../../relational-databases/indexes/how-online-index-operations-work.md).
492492

0 commit comments

Comments
 (0)