From 5f95a30c224109f12876f480f1bf50cb71148cbc Mon Sep 17 00:00:00 2001 From: Greg Low Date: Tue, 30 Jan 2018 15:10:22 +0800 Subject: [PATCH] Minor name change as per Microsoft standard naming --- ...onfigure-the-cursor-threshold-server-configuration-option.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/database-engine/configure-windows/configure-the-cursor-threshold-server-configuration-option.md b/docs/database-engine/configure-windows/configure-the-cursor-threshold-server-configuration-option.md index 3ec26ee1ec6..fefdb38ebda 100644 --- a/docs/database-engine/configure-windows/configure-the-cursor-threshold-server-configuration-option.md +++ b/docs/database-engine/configure-windows/configure-the-cursor-threshold-server-configuration-option.md @@ -54,7 +54,7 @@ ms.workload: "Inactive" ### Recommendations -- This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] technician. +- This option is an advanced option and should be changed only by an experienced database administrator or certified [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] professional. - If you set **cursor threshold** to -1, all keysets are generated synchronously, which benefits small cursor sets. If you set **cursor threshold** to 0, all cursor keysets are generated asynchronously. With other values, the query optimizer compares the number of expected rows in the cursor set and builds the keyset asynchronously if it exceeds the number set in **cursor threshold**. Do not set **cursor threshold** too low, because small result sets are better built synchronously.