More fixes

rothja · rothja · commit 1df9dfd514be · 2020-12-17T10:27:35.000-05:00
diff --git a/docs/ado/guide/appendixes/microsoft-ole-db-persistence-provider-ado-service-provider.md b/docs/ado/guide/appendixes/microsoft-ole-db-persistence-provider-ado-service-provider.md
@@ -44,6 +44,3 @@ The Microsoft OLE DB Persistence Provider enables you to save a [Recordset](../.
  For more information about persistently storing **Recordset** objects, see [Recordset Persistence](../data/more-about-recordset-persistence.md).
 
  When a stream is used to open a **Recordset,** there should be no parameters specified other than the *Source* parameter of the **Open** method.
-
-## See Also
-[Microsoft OLE DB Persistence Provider (ADO Service Provider)]()
diff --git a/docs/ado/guide/remote-data-service/required-client-settings.md b/docs/ado/guide/remote-data-service/required-client-settings.md
@@ -75,6 +75,5 @@ rs.CursorLocation = adUseClient
  [Customization File SQL Section](./customization-file-sql-section.md)   
  [Customization File UserList Section](./customization-file-userlist-section.md)   
  [DataFactory Customization](./datafactory-customization.md)   
- [Required Client Settings]()   
  [Understanding the Customization File](./understanding-the-customization-file.md)   
  [Writing Your Own Customized Handler](./writing-your-own-customized-handler.md)
diff --git a/docs/ado/reference/ado-api/reshape-name-property-dynamic-ado.md b/docs/ado/reference/ado-api/reshape-name-property-dynamic-ado.md
@@ -26,7 +26,7 @@ Specifies a name for the [Recordset](./recordset-object-ado.md) object.
   
  The **Reshape Name** property is primarily intended for use with the re-shaping feature of the [Microsoft Data Shaping Service for OLE DB](../../guide/appendixes/microsoft-data-shaping-service-for-ole-db-ado-service-provider.md) service provider. Names must be unique to participate in re-shaping.  
   
- This property is read-only, but can be set indirectly when a **Recordset** is created. For example, if a clause of a Shape command creates a **Recordset** and gives it an alias name by using the **AS** keyword, the alias is assigned to the **Reshape Name** property. If no alias is declared, the **Reshape Name** property is assigned a unique name generated by the data shaping service. If the alias name is the same as the name of an existing **Recordset**, neither **Recordset** can be reshaped until one of them is released. The default behavior can be changed by setting a unique name in the [Reshape Name]() property on the ADO connection to **True**. Setting this property gives the data shaping service permission to change the user assigned name, if necessary, to ensure uniqueness. For more information about reshaping, see [Microsoft Data Shaping Service for OLE DB (ADO Service Provider)](../../guide/appendixes/microsoft-data-shaping-service-for-ole-db-ado-service-provider.md).  
+ This property is read-only, but can be set indirectly when a **Recordset** is created. For example, if a clause of a Shape command creates a **Recordset** and gives it an alias name by using the **AS** keyword, the alias is assigned to the **Reshape Name** property. If no alias is declared, the **Reshape Name** property is assigned a unique name generated by the data shaping service. If the alias name is the same as the name of an existing **Recordset**, neither **Recordset** can be reshaped until one of them is released. The default behavior can be changed by setting a unique name in the **Reshape Name** property on the ADO connection to **True**. Setting this property gives the data shaping service permission to change the user assigned name, if necessary, to ensure uniqueness. For more information about reshaping, see [Microsoft Data Shaping Service for OLE DB (ADO Service Provider)](../../guide/appendixes/microsoft-data-shaping-service-for-ole-db-ado-service-provider.md).  
   
  Use the **Reshape Name** property when you want to refer to a **Recordset** in a Shape command, or when you do not know the name because it was generated by the Data Shaping Service. In that case, you could generate a SHAPE command by concatenating the command around the string returned by the **Reshape Name** property.  
   
diff --git a/docs/ado/reference/ado-api/save-method.md b/docs/ado/reference/ado-api/save-method.md
@@ -36,7 +36,7 @@ recordset.Save Destination, PersistFormat
  Optional. A [PersistFormatEnum](./persistformatenum.md) value that specifies the format in which the **Recordset** is to be saved (XML or ADTG). The default value is **adPersistADTG**.  
   
 ## Remarks  
- The [Save Method]() method can only be invoked on an open **Recordset**. Use the [Open Method (ADO Recordset)](./open-method-ado-recordset.md) method to later restore the **Recordset** from *Destination*.  
+ The **Save Method** method can only be invoked on an open **Recordset**. Use the [Open Method (ADO Recordset)](./open-method-ado-recordset.md) method to later restore the **Recordset** from *Destination*.  
   
  If the [Filter Property](./filter-property.md) property is in effect for the **Recordset**, then only the rows accessible under the filter are saved. If the **Recordset** is hierarchical, then the current child **Recordset** and its children are saved, including the parent **Recordset**. If the Save method of a child **Recordset** is called, the child and all its children are saved, but the parent is not.  
   
diff --git a/docs/ado/reference/ado-md-api/ado-md-object-model.md b/docs/ado/reference/ado-md-api/ado-md-object-model.md
@@ -26,7 +26,6 @@ This topic describes how objects are represented and related in ADO MD.
  The [Axis](./axis-object-ado-md.md), [Cell](./cell-object-ado-md.md), [Cellset](./cellset-object-ado-md.md), [CubeDef](./cubedef-object-ado-md.md), [Dimension](./dimension-object-ado-md.md), [Hierarchy](./hierarchy-object-ado-md.md), [Level](./level-object-ado-md.md), and [Member](./member-object-ado-md.md) objects each have a standard ADO [Properties](../ado-api/properties-collection-ado.md) collection.  
   
 ## See Also  
- [ADO MD API Reference]()   
  [ADO MD Code Examples](./ado-md-code-examples.md)   
  [ADO MD Collections](./ado-md-collections.md)   
  [ADO MD Enumerated Constants](./ado-md-enumerated-constants.md)   
diff --git a/docs/dea/database-experimentation-assistant-capture-trace.md b/docs/dea/database-experimentation-assistant-capture-trace.md
@@ -128,7 +128,7 @@ If you see an error when you run a trace capture, confirm that:
 
 - The name of the computer running SQL Server is valid. To confirm, try to connect to the computer running SQL Server by using SQL Server Management Studio (SSMS).
 - Your firewall configuration doesn't block connections to the computer running SQL Server.
-- The user has the permissions that are listed in the [Replay FAQ](./database-experimentation-assistant-replay-trace.md?view=sql-server-ver15#frequently-asked-questions-about-trace-replay).
+- The user has the permissions that are listed in the [Replay FAQ](./database-experimentation-assistant-replay-trace.md#frequently-asked-questions-about-trace-replay).
 - The trace name doesn't follow the standard rollover convention (Capture\_1). Instead, try trace names like Capture\_1A or Capture1.
 
 Following are some possible errors you might see and solutions for resolving them:
diff --git a/docs/integration-services/catalog/ssis-catalog.md b/docs/integration-services/catalog/ssis-catalog.md
@@ -451,7 +451,7 @@ To run the **SSIS Server Maintenance Job**, SSIS creates the SQL Server login **
            FROM Executable File = 'C:\Program Files\Microsoft SQL Server\YourSQLServerDefaultCompatibilityLevel\DTS\Binn\Microsoft.SqlServer.IntegrationServices.Server.dll'  
     ```  
 
-    You can find the value for `YourSQLServerDefaultCompatibilityLevel` from a [list of SQL Server default compatibility levels](../../t-sql/statements/alter-database-transact-sql-compatibility-level.md?view=sql-server-ver15#arguments).
+    You can find the value for `YourSQLServerDefaultCompatibilityLevel` from a [list of SQL Server default compatibility levels](../../t-sql/statements/alter-database-transact-sql-compatibility-level.md#arguments).
   
     [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] CLR stored procedures require UNSAFE permissions to be granted to the login because the login requires additional access to restricted resources, such as the Microsoft Win32 API. For more information about the UNSAFE code permission, see [Creating an Assembly](../../relational-databases/clr-integration/assemblies/creating-an-assembly.md).  
 
diff --git a/docs/linux/sql-server-linux-whats-new-2019.md b/docs/linux/sql-server-linux-whats-new-2019.md
@@ -13,15 +13,15 @@ ms.technology: linux
 
 [!INCLUDE [SQL Server - Linux](../includes/applies-to-version/sql-linux.md)]
 
-This article describes the major features and services available for SQL Server 2019 running on Linux. For package downloads and known issues, see the [Release notes](sql-server-linux-release-notes-2019.md?view=sql-server-linux-ver15).
+This article describes the major features and services available for SQL Server 2019 running on Linux. For package downloads and known issues, see the [Release notes](sql-server-linux-release-notes-2019.md).
 
 ## Ubuntu 18.04 supported
 
-Starting with SQL Server 2019 CU3, Ubuntu 18.04 is now supported. Check out our Quickstart on [Installing SQL Server and creating a database on Ubuntu](quickstart-install-connect-ubuntu.md?view=sql-server-linux-ver15).
+Starting with SQL Server 2019 CU3, Ubuntu 18.04 is now supported. Check out our Quickstart on [Installing SQL Server and creating a database on Ubuntu](quickstart-install-connect-ubuntu.md?view=sql-server-linux-ver15&preserve-view=true).
 
 ## RHEL 8 supported
 
-Starting with SQL Server 2019 CU1, RHEL 8 is now supported. Check out our Quickstart on [Installing SQL Server and creating a database on Red Hat](quickstart-install-connect-red-hat.md?view=sql-server-linux-ver15).
+Starting with SQL Server 2019 CU1, RHEL 8 is now supported. Check out our Quickstart on [Installing SQL Server and creating a database on Red Hat](quickstart-install-connect-red-hat.md?view=sql-server-linux-ver15&preserve-view=true).
 
 ## Updates
 
@@ -43,10 +43,10 @@ The updates have been made in SQL Server 2019 on Linux:
 
 To install SQL Server on Linux, use one of the following tutorials:
 
-- [Install on Red Hat Enterprise Linux](quickstart-install-connect-red-hat.md?view=sql-server-linux-ver15)
-- [Install on SUSE Linux Enterprise Server](quickstart-install-connect-suse.md?view=sql-server-linux-ver15)
-- [Install on Ubuntu](quickstart-install-connect-ubuntu.md?view=sql-server-linux-ver15)
-- [Run on Docker](quickstart-install-connect-docker.md?view=sql-server-linux-ver15)
+- [Install on Red Hat Enterprise Linux](quickstart-install-connect-red-hat.md?view=sql-server-linux-ver15&preserve-view=true)
+- [Install on SUSE Linux Enterprise Server](quickstart-install-connect-suse.md?view=sql-server-linux-ver15&preserve-view=true)
+- [Install on Ubuntu](quickstart-install-connect-ubuntu.md?view=sql-server-linux-ver15&preserve-view=true)
+- [Run on Docker](quickstart-install-connect-docker.md?view=sql-server-linux-ver15&preserve-view=true)
 - [Provision a SQL VM in Azure](/azure/virtual-machines/linux/sql/provision-sql-server-linux-virtual-machine?toc=/sql/toc/toc.json)
 
 For answers to frequently asked questions, see the [SQL Server on Linux FAQ](sql-server-linux-faq.md). To see other improvements introduced in SQL Server 2019, see [What's New in SQL Server 2019](../sql-server/what-s-new-in-sql-server-ver15.md?view=sql-server-ver15&preserve-view=true).
diff --git a/docs/relational-databases/in-memory-oltp/sample-database-for-in-memory-oltp.md b/docs/relational-databases/in-memory-oltp/sample-database-for-in-memory-oltp.md
@@ -20,7 +20,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
  This sample showcases the In-Memory OLTP feature. It shows  memory-optimized tables and natively compiled stored procedures, and can be used to demonstrate performance benefits of In-Memory OLTP.  
   
 > [!NOTE]  
->  To view this topic for [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)], see [Extensions to AdventureWorks to Demonstrate In-Memory OLTP](./overview-and-usage-scenarios.md?view=sql-server-ver15#in-memory-oltp-overview).  
+>  To view this topic for [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)], see [Extensions to AdventureWorks to Demonstrate In-Memory OLTP](./overview-and-usage-scenarios.md#in-memory-oltp-overview).  
   
  The sample migrates five tables in the AdventureWorks database to memory-optimized, and it includes a demo workload for sales order processing. You can use this demo workload to see the performance benefit of using In-Memory OLTP on your server.  
   
diff --git a/docs/relational-databases/system-tables/system-base-tables.md b/docs/relational-databases/system-tables/system-base-tables.md
@@ -94,4 +94,4 @@ Msg 3859: Warning: The system catalog was updated directly in database ID 17, mo
 ### Executing the DBCC_CHECKDB command after a system table is manually updated
 Msg 3859: Warning: The system catalog was updated directly in database ID 17, most recently at date_time.
 
-If you perform manual updates to a system table and encounter a problem, you might be asked to restore from a backup or copy out the data from the affected database to a new database. Learn more about [user action error messages](../errors-events/mssqlserver-8992-database-engine-error.md?view=sql-server-ver15#user-action).
+If you perform manual updates to a system table and encounter a problem, you might be asked to restore from a backup or copy out the data from the affected database to a new database. Learn more about [user action error messages](../errors-events/mssqlserver-8992-database-engine-error.md#user-action).
diff --git a/docs/sql-server/what-s-new-in-sql-server-ver15.md b/docs/sql-server/what-s-new-in-sql-server-ver15.md
@@ -216,8 +216,8 @@ The easiest way to get started working with [!INCLUDE[ssNoVersion](../includes/s
 
 |New feature or update | Details |
 |:---|:---| 
-|New memory setup options | Sets the *min server memory (MB)* and *max server memory (MB)* server configurations during installation. See [Database Engine Configuration - Memory page](https://docs.microsoft.com/sql/sql-server/install/instance-configuration?view=sql-server-ver15#memory) and the `USESQLRECOMMENDEDMEMORYLIMITS`, `SQLMINMEMORY`, and `SQLMAXMEMORY` parameters in [Install SQL Server from the Command Prompt](../database-engine/install-windows/install-sql-server-from-the-command-prompt.md#Install). The proposed value aligns with the memory configuration guidelines in [Server Memory Configuration Options](../database-engine/configure-windows/server-memory-server-configuration-options.md#manually).| 
-|New parallelism setup options | Sets the *max degree of parallelism* server configuration during installation. See [Database Engine Configuration - MaxDOP page](https://docs.microsoft.com/sql/sql-server/install/instance-configuration?view=sql-server-ver15#maxdop) and the `SQLMAXDOP` parameter in [Install SQL Server from the Command Prompt](../database-engine/install-windows/install-sql-server-from-the-command-prompt.md#Install). The default value aligns with the max degree of parallelism guidelines in [Configure the max degree of parallelism Server Configuration Option](../database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option.md#Guidelines).| 
+|New memory setup options | Sets the *min server memory (MB)* and *max server memory (MB)* server configurations during installation. See [Database Engine Configuration - Memory page](https://docs.microsoft.com/sql/sql-server/install/instance-configuration#memory) and the `USESQLRECOMMENDEDMEMORYLIMITS`, `SQLMINMEMORY`, and `SQLMAXMEMORY` parameters in [Install SQL Server from the Command Prompt](../database-engine/install-windows/install-sql-server-from-the-command-prompt.md#Install). The proposed value aligns with the memory configuration guidelines in [Server Memory Configuration Options](../database-engine/configure-windows/server-memory-server-configuration-options.md#manually).| 
+|New parallelism setup options | Sets the *max degree of parallelism* server configuration during installation. See [Database Engine Configuration - MaxDOP page](./install/instance-configuration#maxdop) and the `SQLMAXDOP` parameter in [Install SQL Server from the Command Prompt](../database-engine/install-windows/install-sql-server-from-the-command-prompt.md#Install). The default value aligns with the max degree of parallelism guidelines in [Configure the max degree of parallelism Server Configuration Option](../database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option.md#Guidelines).| 
 |Setup warning on Server/CAL license Product Key|If an Enterprise Server/CAL license Product Key is entered, and the machine has more than 20 physical cores, or 40 logical cores when Hyper-Threading is enabled, a warning is shown during setup. Users can still acknowledge the limitation and continue setup, or enter a License Key that supports the operating system maximum number of processors.|
 | &nbsp; | &nbsp; |
 
