fixed regex problem

Michael Blome · Michael Blome · commit b63393dc0d00 · 2018-08-30T13:39:36.000-07:00
diff --git a/docs/2014/analysis-services/instances/configure-service-accounts-analysis-services.md b/docs/2014/analysis-services/instances/configure-service-accounts-analysis-services.md
@@ -54,7 +54,7 @@ manager: craigg
  The sole member of the group is the per-service SID. Right next to it is the logon account. The logon account name is cosmetic, there to provide context to the per-service SID. If you subsequently change the logon account and then return to this page, you'll notice that the security group and per-service SID do not change, but the logon account label is different.  
   
 ##  <a name="bkmk_winpriv"></a> Windows privileges assigned to the Analysis Services service account  
- Analysis Services needs permissions from the operating system for service startup and to request system resources. Requirements vary by server mode and whether the instance is clustered. If you are unfamiliar with Windows privileges, see [Privileges](http://msdn.microsoft.com/library/windows/desktop/aa379306\(v=vs.85\).aspx) and [Privilege Constants (Windows)](/windows/desktop/SecAuthZ/privilege-constants).aspx) for details.  
+ Analysis Services needs permissions from the operating system for service startup and to request system resources. Requirements vary by server mode and whether the instance is clustered. If you are unfamiliar with Windows privileges, see [Privileges](http://msdn.microsoft.com/library/windows/desktop/aa379306\(v=vs.85\).aspx) and [Privilege Constants (Windows)](/windows/desktop/SecAuthZ/privilege-constants) for details.  
   
  All instances of Analysis Services require the **Log on as a service** (SeServiceLogonRight) privilege. SQL Server Setup assigns the privilege for you on the service account specified during installation. For servers running in Multidimensional and Data Mining mode, this is the only Windows privilege required by the Analysis Services service account for standalone server installations, and it is the only privilege that Setup configures for Analysis Services. For clustered and tabular instances, additional Windows privileges must be added manually.  
   
@@ -150,8 +150,8 @@ manager: craigg
  [Configure Windows Service Accounts and Permissions](../../database-engine/configure-windows/configure-windows-service-accounts-and-permissions.md)   
  [SQL Server Service Account and Per-Service SID (Blog)](http://www.travisgan.com/2013/06/sql-server-service-account-and-per.html)   
  [SQL Server uses a service SID to provide service isolation (KB Article)](http://support.microsoft.com/kb/2620201)   
- [Access Token (MSDN)](/windows/desktop/SecAuthZ/access-tokens).aspx)   
- [Security Identifiers (MSDN)](/windows/desktop/SecAuthZ/security-identifiers).aspx)   
+ [Access Token (MSDN)](/windows/desktop/SecAuthZ/access-tokens)   
+ [Security Identifiers (MSDN)](/windows/desktop/SecAuthZ/security-identifiers)   
  [Access Token (Wikipedia)](http://en.wikipedia.org/wiki/Access_token)   
  [Access Control Lists (Wikipedia)](http://en.wikipedia.org/wiki/Access_control_list)  
   
diff --git a/docs/2014/analysis-services/multidimensional-models/olap-physical/object-naming-rules-analysis-services.md b/docs/2014/analysis-services/multidimensional-models/olap-physical/object-naming-rules-analysis-services.md
@@ -67,7 +67,7 @@ manager: craigg
   
 |Object|Invalid characters|  
 |------------|------------------------|  
-|`Server`|Follow Windows server naming conventions when naming a server object. See [Naming Conventions (Windows)](/windows/desktop/DNS/naming-conventions).aspx) for details.|  
+|`Server`|Follow Windows server naming conventions when naming a server object. See [Naming Conventions (Windows)](/windows/desktop/DNS/naming-conventions) for details.|  
 |`DataSource`|: / \ * &#124; ? " () [] {} <>|  
 |`Level` or `Attribute`|. , ; ' ` : / \ * &#124; ? " & % $ ! + = [] {} \< >|  
 |`Dimension` or `Hierarchy`|. , ; ' ` : / \ * &#124; ? " & % $ ! + = () [] {} \<,>|  
diff --git a/docs/2014/relational-databases/in-memory-oltp/determining-if-a-table-or-stored-procedure-should-be-ported-to-in-memory-oltp.md b/docs/2014/relational-databases/in-memory-oltp/determining-if-a-table-or-stored-procedure-should-be-ported-to-in-memory-oltp.md
@@ -120,7 +120,7 @@ manager: craigg
   
  A data collector can be configured on a SQL Server 2012 or later version of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)].  
   
- You need a [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Agent proxy established with the correct credential for a data collector to upload data to a Management Data Warehouse database on an instance that is different from where transactions will be profiled. To enable a [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Agent proxy, you must first establish a credential with a domain-enabled login. The domain-enabled login must be a member of `mdw_admin` group for the Management Data Warehouse database. See [How to: Create a Credential (SQL Server Management Studio)](../security/authentication-access/create-a-credential.md).aspx) for information on how to create a credential.  
+ You need a [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Agent proxy established with the correct credential for a data collector to upload data to a Management Data Warehouse database on an instance that is different from where transactions will be profiled. To enable a [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Agent proxy, you must first establish a credential with a domain-enabled login. The domain-enabled login must be a member of `mdw_admin` group for the Management Data Warehouse database. See [How to: Create a Credential (SQL Server Management Studio)](../security/authentication-access/create-a-credential.md) for information on how to create a credential.  
   
  To configure data collection to upload to a Management Data Warehouse database on a different instance,  
   
diff --git a/docs/analysis-services/instances/configure-service-accounts-analysis-services.md b/docs/analysis-services/instances/configure-service-accounts-analysis-services.md
@@ -45,7 +45,7 @@ manager: kfile
  The sole member of the group is the per-service SID. Right next to it is the logon account. The logon account name is cosmetic, there to provide context to the per-service SID. If you subsequently change the logon account and then return to this page, you'll notice that the security group and per-service SID do not change, but the logon account label is different.  
   
 ##  <a name="bkmk_winpriv"></a> Windows privileges assigned to the Analysis Services service account  
- Analysis Services needs permissions from the operating system for service startup and to request system resources. Requirements vary by server mode and whether the instance is clustered. If you are unfamiliar with Windows privileges, see [Privileges](http://msdn.microsoft.com/library/windows/desktop/aa379306\(v=vs.85\).aspx) and [Privilege Constants (Windows)](/windows/desktop/SecAuthZ/privilege-constants).aspx) for details.  
+ Analysis Services needs permissions from the operating system for service startup and to request system resources. Requirements vary by server mode and whether the instance is clustered. If you are unfamiliar with Windows privileges, see [Privileges](http://msdn.microsoft.com/library/windows/desktop/aa379306\(v=vs.85\).aspx) and [Privilege Constants (Windows)](/windows/desktop/SecAuthZ/privilege-constants) for details.  
   
  All instances of Analysis Services require the **Log on as a service** (SeServiceLogonRight) privilege. SQL Server Setup assigns the privilege for you on the service account specified during installation. For servers running in Multidimensional and Data Mining mode, this is the only Windows privilege required by the Analysis Services service account for standalone server installations, and it is the only privilege that Setup configures for Analysis Services. For clustered and tabular instances, additional Windows privileges must be added manually.  
   
@@ -141,8 +141,8 @@ manager: kfile
  [Configure Windows Service Accounts and Permissions](../../database-engine/configure-windows/configure-windows-service-accounts-and-permissions.md)   
  [SQL Server Service Account and Per-Service SID (Blog)](http://www.travisgan.com/2013/06/sql-server-service-account-and-per.html)   
  [SQL Server uses a service SID to provide service isolation (KB Article)](http://support.microsoft.com/kb/2620201)   
- [Access Token (MSDN)](/windows/desktop/SecAuthZ/access-tokens).aspx)   
- [Security Identifiers (MSDN)](/windows/desktop/SecAuthZ/security-identifiers).aspx)   
+ [Access Token (MSDN)](/windows/desktop/SecAuthZ/access-tokens)   
+ [Security Identifiers (MSDN)](/windows/desktop/SecAuthZ/security-identifiers)   
  [Access Token (Wikipedia)](http://en.wikipedia.org/wiki/Access_token)   
  [Access Control Lists (Wikipedia)](http://en.wikipedia.org/wiki/Access_control_list)  
   
diff --git a/docs/analysis-services/multidimensional-models/olap-physical/object-naming-rules-analysis-services.md b/docs/analysis-services/multidimensional-models/olap-physical/object-naming-rules-analysis-services.md
@@ -60,7 +60,7 @@ manager: kfile
   
 |Object|Invalid characters|  
 |------------|------------------------|  
-|**Server**|Follow Windows server naming conventions when naming a server object. See [Naming Conventions (Windows)](/windows/desktop/DNS/naming-conventions).aspx) for details.|  
+|**Server**|Follow Windows server naming conventions when naming a server object. See [Naming Conventions (Windows)](/windows/desktop/DNS/naming-conventions) for details.|  
 |**DataSource**|: / \ * &#124; ? " () [] {} <>|  
 |**Level** or **Attribute**|. , ; ' ` : / \ * &#124; ? " & % $ ! + = [] {} < >|  
 |**Dimension** or **Hierarchy**|. , ; ' ` : / \ * &#124; ? " & % $ ! + = () [] {} \<,>|  
diff --git a/docs/database-engine/install-windows/install-sql-server-from-the-installation-wizard-setup.md b/docs/database-engine/install-windows/install-sql-server-from-the-installation-wizard-setup.md
@@ -23,7 +23,7 @@ manager: craigg
 
 [!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md-winonly](../../includes/appliesto-ss-xxxx-xxxx-xxx-md-winonly.md)]
  
-This article explains how to install SQL Server with the Installation Wizard. It applies to [!INCLUDE[SQLServer2016](../../includes/sssql15-md.md)], and [!INCLUDE[SQLServer2017](../../includes/sssqlv14-md.md)]. For content related to previous versions of SQL Server, see [Install SQL Server 2014 from the Installation Wizard (Setup)](install-sql-server-from-the-installation-wizard-setup.md).aspx).
+This article explains how to install SQL Server with the Installation Wizard. It applies to [!INCLUDE[SQLServer2016](../../includes/sssql15-md.md)], and [!INCLUDE[SQLServer2017](../../includes/sssqlv14-md.md)]. For content related to previous versions of SQL Server, see [Install SQL Server 2014 from the Installation Wizard (Setup)](install-sql-server-from-the-installation-wizard-setup.md).
 
 This article provides a step-by-step procedure for installing a new instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] using the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] setup installation wizard. The [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Installation Wizard provides a single feature tree for installation of all [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] components so that you do not have to install them individually. For more information about how to install the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] components individually, see [Install SQL Server](../../database-engine/install-windows/install-sql-server.md#how-to-install-individual-components).  
 
diff --git a/docs/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md b/docs/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md
@@ -106,7 +106,7 @@ manager: craigg
 -   Constraints on resources, such as: hardware, personnel, space for storing backup media, the physical security of the stored media, and so on.  
 
 ### Impact of the recovery model on backup and restore  
- Backup and restore operations occur within the context of a recovery model. A recovery model is a database property that controls how the transaction log is managed. Also, the recovery model of a database determines what types of backups and what restore scenarios are supported for the database. Typically a database uses either the simple recovery model or the full recovery model. The full recovery model can be supplemented by switching to the bulk-logged recovery model before bulk operations. For an introduction to these recovery models and how they affect transaction log management, see [The Transaction Log (SQL Server)](../logs/the-transaction-log-sql-server.md).aspx)  
+ Backup and restore operations occur within the context of a recovery model. A recovery model is a database property that controls how the transaction log is managed. Also, the recovery model of a database determines what types of backups and what restore scenarios are supported for the database. Typically a database uses either the simple recovery model or the full recovery model. The full recovery model can be supplemented by switching to the bulk-logged recovery model before bulk operations. For an introduction to these recovery models and how they affect transaction log management, see [The Transaction Log (SQL Server)](../logs/the-transaction-log-sql-server.md)  
   
  The best choice of recovery model for the database depends on your business requirements. To avoid transaction log management and simplify backup and restore, use the simple recovery model. To minimize work-loss exposure, at the cost of administrative overhead, use the full recovery model. For information about the effect of recovery models on backup and restore, see [Backup Overview &#40;SQL Server&#41;](../../relational-databases/backup-restore/backup-overview-sql-server.md).  
   
diff --git a/docs/relational-databases/backup-restore/create-a-full-database-backup-sql-server.md b/docs/relational-databases/backup-restore/create-a-full-database-backup-sql-server.md
@@ -22,7 +22,7 @@ manager: craigg
 ---
 # Create a Full Database Backup (SQL Server)
 [!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
- > For SQL Server 2014, go to [Create a Full Database Backup (SQL Server)](create-a-full-database-backup-sql-server.md).aspx).
+ > For SQL Server 2014, go to [Create a Full Database Backup (SQL Server)](create-a-full-database-backup-sql-server.md).
 
   This topic describes how to create a full database backup in [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] using [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)], [!INCLUDE[tsql](../../includes/tsql-md.md)], or PowerShell.  
   
diff --git a/docs/relational-databases/data-collection/data-collection.md b/docs/relational-databases/data-collection/data-collection.md
@@ -114,7 +114,7 @@ manager: craigg
 |Manage different aspects of data collection, such as enabling or disabling data collection, changing a collection set configuration, or viewing data in the management data warehouse.|[Manage Data Collection](../../relational-databases/data-collection/manage-data-collection.md)|  
 |Use reports to obtain information for monitoring system capacity and troubleshooting system performance.|[System Data Collection Set Reports](../../relational-databases/data-collection/system-data-collection-set-reports.md)|  
 |Use the Management Data Warehouse to collect data from a server that is a data collection target.|[Management Data Warehouse](../../relational-databases/data-collection/management-data-warehouse.md)| 
-|Exploit the server-side trace capabilities of SQL Server Profiler to export a trace definition that you can use to create a collection set that uses the Generic SQL Trace collector type| [Use SQL Server Profiler to Create a SQL Trace Collection Set (SQL Server Management Studio)](use-sql-server-profiler-to-create-a-sql-trace-collection-set.md).aspx)
+|Exploit the server-side trace capabilities of SQL Server Profiler to export a trace definition that you can use to create a collection set that uses the Generic SQL Trace collector type| [Use SQL Server Profiler to Create a SQL Trace Collection Set (SQL Server Management Studio)](use-sql-server-profiler-to-create-a-sql-trace-collection-set.md)
   
   
 
diff --git a/docs/relational-databases/linked-servers/create-linked-servers-sql-server-database-engine.md b/docs/relational-databases/linked-servers/create-linked-servers-sql-server-database-engine.md
@@ -26,7 +26,7 @@ manager: craigg
 ---
 # Create Linked Servers (SQL Server Database Engine)
 [!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
- > For content related to previous versions of SQL Server, see [Create Linked Servers (SQL Server Database Engine)](create-linked-servers-sql-server-database-engine.md).aspx).
+ > For content related to previous versions of SQL Server, see [Create Linked Servers (SQL Server Database Engine)](create-linked-servers-sql-server-database-engine.md).
 
   This topic shows how to create a linked server and access data from another [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] by using [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] or [!INCLUDE[tsql](../../includes/tsql-md.md)]. By creating a linked server,  you can work with data from multiple sources. The linked server does not have to be another instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], but that is a common scenario.  
   
diff --git a/docs/relational-databases/security/encryption/transparent-data-encryption.md b/docs/relational-databases/security/encryption/transparent-data-encryption.md
@@ -23,7 +23,7 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 # Transparent Data Encryption (TDE)
 [!INCLUDE[appliesto-ss-asdb-asdw-pdw-md](../../../includes/appliesto-ss-asdb-asdw-pdw-md.md)]
 
- > For content related to previous versions of SQL Server, see [Transparent Data Encryption (TDE)](transparent-data-encryption-tde.md).aspx).
+ > For content related to previous versions of SQL Server, see [Transparent Data Encryption (TDE)](transparent-data-encryption-tde.md).
 
   *Transparent Data Encryption* (TDE) encrypts [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], [!INCLUDE[ssSDSFull](../../../includes/sssdsfull-md.md)], and [!INCLUDE[ssSDWfull](../../../includes/sssdwfull-md.md)] data files, known as encrypting data at rest. You can take several precautions to help secure the database such as designing a secure system, encrypting confidential assets, and building a firewall around the database servers. However, in a scenario where the physical media (such as drives or backup tapes) are stolen, a malicious party can just restore or attach the database and browse the data. One solution is to encrypt the sensitive data in the database and protect the keys that are used to encrypt the data with a certificate. This prevents anyone without the keys from using the data, but this kind of protection must be planned in advance.  
   
diff --git a/docs/relational-databases/system-dynamic-management-views/sys-dm-os-host-info-transact-sql.md b/docs/relational-databases/system-dynamic-management-views/sys-dm-os-host-info-transact-sql.md
@@ -33,7 +33,7 @@ Returns one row that displays operating system version information.
 |-----------------|---------------|-----------------|  
 |**host_platform** |**nvarchar(256)** |The type of operating system: Windows or Linux |
 |**host_distribution** |**nvarchar(256)** |Description of the operating system. |
-|**host_release**|**nvarchar(256)**|[!INCLUDE[msCoName](../../includes/msconame-md.md)] Windows operating system release (version number). For a list of values and descriptions, see [Operating System Version (Windows)](/windows/desktop/SysInfo/operating-system-version).aspx). <br> For Linux, returns an empty string. |  
+|**host_release**|**nvarchar(256)**|[!INCLUDE[msCoName](../../includes/msconame-md.md)] Windows operating system release (version number). For a list of values and descriptions, see [Operating System Version (Windows)](/windows/desktop/SysInfo/operating-system-version). <br> For Linux, returns an empty string. |  
 |**host_service_pack_level**|**nvarchar(256)**|Service pack level of the Windows operating system. <br> For Linux, returns an empty string. |  
 |**host_sku**|**int**|Windows Stock Keeping Unit (SKU) ID. For a list of SKU IDs and descriptions, see [GetProductInfo Function](http://msdn.microsoft.com/library/ms724358.aspx). Is nullable. <br> For Linux, returns NULL. |  
 |**os_language_version**|**int**|Windows locale identifier (LCID) of the operating system. For a list of LCID values and descriptions, see [Locale IDs Assigned by Microsoft](http://go.microsoft.com/fwlink/?LinkId=208080). Cannot be null.|  
diff --git a/docs/relational-databases/system-dynamic-management-views/sys-dm-os-windows-info-transact-sql.md b/docs/relational-databases/system-dynamic-management-views/sys-dm-os-windows-info-transact-sql.md
@@ -32,7 +32,7 @@ manager: craigg
   
 |Column name|Data type|Description|  
 |-----------------|---------------|-----------------|  
-|**windows_release**|**nvarchar(256)**|For Windows, returns the release number. For a list of values and descriptions, see [Operating System Version (Windows)](/windows/desktop/SysInfo/operating-system-version).aspx). Cannot be NULL.|  
+|**windows_release**|**nvarchar(256)**|For Windows, returns the release number. For a list of values and descriptions, see [Operating System Version (Windows)](/windows/desktop/SysInfo/operating-system-version). Cannot be NULL.|  
 |**windows_service_pack_level**|**nvarchar(256)**| For Windows, returns the service pack number. Cannot be NULL. |  
 |**windows_sku**|**int**|For Windows, returns the Windows Stock Keeping Unit (SKU) ID. For a list of SKU IDs and descriptions, see [GetProductInfo Function](http://msdn.microsoft.com/library/ms724358.aspx). Is NULLable. |  
 |**os_language_version**|**int**| For Windows, returns the Windows locale identifier (LCID) of the operating system. For a list of LCID values and descriptions, see [Locale IDs Assigned by Microsoft](http://go.microsoft.com/fwlink/?LinkId=208080). Cannot be NULL.|  
diff --git a/docs/relational-databases/system-stored-procedures/sp-dropalias-transact-sql.md b/docs/relational-databases/system-stored-procedures/sp-dropalias-transact-sql.md
diff --git a/docs/relational-databases/tables/add-columns-to-a-table-database-engine.md b/docs/relational-databases/tables/add-columns-to-a-table-database-engine.md
diff --git a/docs/relational-databases/user-defined-functions/create-user-defined-functions-database-engine.md b/docs/relational-databases/user-defined-functions/create-user-defined-functions-database-engine.md
diff --git a/docs/relational-databases/xml/for-xml-sql-server.md b/docs/relational-databases/xml/for-xml-sql-server.md
diff --git a/docs/reporting-services/lesson-1-creating-a-report-server-project-reporting-services.md b/docs/reporting-services/lesson-1-creating-a-report-server-project-reporting-services.md
diff --git a/docs/sql-server/install/uninstall-an-existing-instance-of-sql-server-setup.md b/docs/sql-server/install/uninstall-an-existing-instance-of-sql-server-setup.md
