Merge pull request #10452 from craigcaseyMSFT/vcraic0530

fixes for broken link report

Author: rmca14

docs/2014/2014-toc/books-online-for-sql-server-2014.md

@@ -51,7 +51,7 @@ SQL Server 2016, and later versions, are documented [here](https://docs.microsof
 
 -   [SQL Server on Microsoft.com](https://go.microsoft.com/fwlink/?linkid=8504)  
 
--   [SQL Server Resource Center](https://go.microsoft.com/fwlink/?linkid=218841)  
+-   [SQL Server Resource Center](https://www.microsoft.com/sql-server/sql-server-2017-resources)  
 
 -   [SQL Server TechCenter](https://go.microsoft.com/fwlink/?linkid=28107)  
 

docs/analysis-services/instances/connection-string-properties-analysis-services.md

@@ -61,7 +61,7 @@ manager: kfile
 
 |Property|Description|  
 |--------------|-----------------|  
-|**Application Name**|Sets the name of the application associated with the connection. This value can be useful when monitoring tracing events, especially when you have several applications accessing the same databases. For example, adding Application Name='test' to a connection string causes 'test' to appear in a SQL Server Profiler trace, as shown in the following screenshot:<br /><br /> ![SSAS_AppNameExcample](../../analysis-services/instances/media/ssas-appnameexcample.gif "SSAS_AppNameExcample")<br /><br /> Aliases for this property include **sspropinitAppName**, **AppName**. For more information, see [Use Application Name parameter when connecting to SQL Server](http://go.microsoft.com/fwlink/?LinkId=301699).|  
+|**Application Name**|Sets the name of the application associated with the connection. This value can be useful when monitoring tracing events, especially when you have several applications accessing the same databases. For example, adding Application Name='test' to a connection string causes 'test' to appear in a SQL Server Profiler trace, as shown in the following screenshot:<br /><br /> ![SSAS_AppNameExcample](../../analysis-services/instances/media/ssas-appnameexcample.gif "SSAS_AppNameExcample")<br /><br /> Aliases for this property include **sspropinitAppName**, **AppName**. For more information, see [Use Application Name parameter when connecting to SQL Server](https://www.connectionstrings.com/use-application-name-sql-server/).|  
 |**AutoSyncPeriod**|Sets the frequency (in milliseconds) of client and server cache synchronization. ADOMD.NET provides client caching for frequently used objects that have minimal memory overhead. This helps reduce the number of round trips to the server. The default is 10000 milliseconds (or 10 seconds). When set to null or 0, automatic synchronization is turned off.|  
 |**Character Encoding**|Defines how characters are encoded on the request. Valid values are Default or UTF-8 (these are equivalent), and UTF-16| 
 |**CommitTimeout**|An XMLA property. Determines how long, in milliseconds, the commit phase of a currently running command waits before rolling back. When greater than 0, overrides the value of the corresponding CommitTimeout property in the server configuration. |   

docs/database-engine/whats-new-in-sql-server-2016.md

@@ -438,7 +438,7 @@ Download the latest [SQL Server Management Studio (SSMS)](../ssms/download-sql-s
 ### Upgrade Advisor
 SQL Server 2016 Upgrade Advisor Preview is a standalone tool that enables users of prior versions to run a set of upgrade rules against their SQL Server database to pinpoint breaking and behavior changes and deprecated features as well as providing help with the adoption of new features such as Stretch Database.
 
- You can download Upgrade Advisor Preview [here](https://www.microsoft.com/download/details.aspx?id=48119) or you can install it by using the Web Platform Installer.
+ You can download Upgrade Advisor Preview [here](https://docs.microsoft.com/sql/sql-server/install/use-upgrade-advisor-to-prepare-for-upgrades#how-to-install-and-run-upgrade-advisor) or you can install it by using the Web Platform Installer.
 
 ## See Also
 [What's New in SQL Server 2016](../sql-server/what-s-new-in-sql-server-2016.md)

docs/dma/dma-sku-recommend-sql-db.md

@@ -36,7 +36,7 @@ The following are instructions to help you determine the Azure SQL Database SKU
 
 ## Prerequisites
 
-- Download and install the latest version of [DMA](https://aka.sm/get-dma). If you have already an earlier version of the tool, open it, and you'll be prompted to upgrade DMA.
+- Download and install the latest version of [DMA](https://aka.ms/get-dma). If you have already an earlier version of the tool, open it, and you'll be prompted to upgrade DMA.
 - Ensure that your computer has [PowerShell Version 5.1](https://www.microsoft.com/download/details.aspx?id=54616) or later, which is required to run all scripts. For information about findoug out which version of PowerShell is installed on your computer, see the article [Download and install Windows PowerShell 5.1](https://docs.microsoft.com/skypeforbusiness/set-up-your-computer-for-windows-powershell/download-and-install-windows-powershell-5-1).
 - Ensure that your computer has the Azure Powershell Module installed. For more information, see the article [Install the Azure PowerShell module](https://docs.microsoft.com/powershell/azure/install-az-ps?view=azps-1.8.0).
 - Verify that the PowerShell file **SkuRecommendationDataCollectionScript.ps1**, which is required to collect the performance counters, is installed in the DMA folder.

docs/linux/sql-server-linux-active-directory-join-domain.md

@@ -134,7 +134,7 @@ This method joins the SQL Server host to an AD domain using **realmd** and **sss
 
 Use the following steps to join a SQL Server host to an Active Directory domain:
 
-1. Use [realmd](https://www.freedesktop.org/software/realmd/docs/guide-active-directory-join.md) to join your host machine to your AD Domain. You must first install both the **realmd** and Kerberos client packages on the SQL Server host machine using your Linux distribution's package manager:
+1. Use [realmd](https://www.freedesktop.org/software/realmd/docs/guide-active-directory-join) to join your host machine to your AD Domain. You must first install both the **realmd** and Kerberos client packages on the SQL Server host machine using your Linux distribution's package manager:
 
    **RHEL:**
 
@@ -174,7 +174,7 @@ Use the following steps to join a SQL Server host to an Active Directory domain:
 
    SQL Server uses SSSD and NSS for mapping user accounts and groups to security identifiers (SIDs). SSSD must be configured and running for SQL Server to create AD logins successfully. **realmd** usually does this automatically as part of joining the domain, but in some cases, you must do this separately.
 
-   For more information, see how to [configure SSSD manually](https://access.redhat.com/articles/3023951), and [configure NSS to work with SSSD](https://access.redhat.com/documentation/red_hat_enterprise_linux/7/html/system-level_authentication_guide/configuring_services#Configuration_Options-NSS_Configuration_Options).
+   For more information, see how to [configure SSSD manually](https://access.redhat.com/articles/3023951), and [configure NSS to work with SSSD](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system-level_authentication_guide/configuring_services#Configuration_Options-NSS_Configuration_Options).
 
 1. Verify that you can now gather information about a user from the domain, and that you can acquire a Kerberos ticket as that user. The following example uses **id**, [kinit](https://web.mit.edu/kerberos/krb5-1.12/doc/user/user_commands/kinit.html), and [klist](https://web.mit.edu/kerberos/krb5-1.12/doc/user/user_commands/klist.html) commands for this.
 

docs/relational-databases/security/encryption/rotate-always-encrypted-keys-using-powershell.md

@@ -116,7 +116,7 @@ The Security Administrator generates a new column master key, re-encrypts the im
 |Step 2. Create a new column master key in a key store.<br><br>**Note:** The SqlServer module does not support this step. To accomplish this task from a command-line, you need to use the tools that are specific the type of your key store.|[Creating and Storing Column Master Keys (Always Encrypted)](../../../relational-databases/security/encryption/create-and-store-column-master-keys-always-encrypted.md)| Yes | No
 |Step 3. Start a PowerShell environment and import the SqlServer module. | [Import the SqlServer module](../../../relational-databases/security/encryption/configure-always-encrypted-using-powershell.md#importsqlservermodule) | No | No
 |Step 4. Create a SqlColumnMasterKeySettings object that contains information about the location of your **old** column master key. SqlColumnMasterKeySettings is an object that exists in memory (in PowerShell). |New-SqlColumnMasterKeySettings| No | No
-|Step 5. Create a SqlColumnMasterKeySettings object that contains information about the location of your **new** column master key. SqlColumnMasterKeySettings is an object that exists in memory (in PowerShell). To create it, you need to use the cmdlet that is specific to your key store. | [New-SqlAzureKeyVaultColumnMasterKeySettings](https://docs.microsoft.com/powershell/sqlserver/sqlserver/vlatest/new-sqlazurekeyvaultcolumnmasterkeysettings)<br><br>[New-SqlCertificateStoreColumnMasterKeySettings](https://msdn.microsoft.com/library/mt759816.aspx)<br><br>[New-SqlCngColumnMasterKeySettings](https://docs.microsoft.com/powershell/sqlserver/sqlserver/vlatest/new-sqlcngcolumnmasterkeysettings)<br><br>[New-SqlCspColumnMasterKeySettings](https://docs.microsoft.com/powershell/sqlserver/sqlserver/vlatest/new-sqlcspcolumnmasterkeysettings)| No | No
+|Step 5. Create a SqlColumnMasterKeySettings object that contains information about the location of your **new** column master key. SqlColumnMasterKeySettings is an object that exists in memory (in PowerShell). To create it, you need to use the cmdlet that is specific to your key store. | [New-SqlAzureKeyVaultColumnMasterKeySettings](https://docs.microsoft.com/powershell/sqlserver/sqlserver/vlatest/new-sqlazurekeyvaultcolumnmasterkeysettings)<br><br>[New-SqlCertificateStoreColumnMasterKeySettings](https://docs.microsoft.com/powershell/sqlserver/sqlserver/vlatest/new-sqlcertificatestorecolumnmasterkeysettings)<br><br>[New-SqlCngColumnMasterKeySettings](https://docs.microsoft.com/powershell/sqlserver/sqlserver/vlatest/new-sqlcngcolumnmasterkeysettings)<br><br>[New-SqlCspColumnMasterKeySettings](https://docs.microsoft.com/powershell/sqlserver/sqlserver/vlatest/new-sqlcspcolumnmasterkeysettings)| No | No
 |Step 6. Authenticate to Azure, if your old (current) column master key or your new column master key is stored in Azure Key Vault. | [Add-SqlAzureAuthenticationContext](https://docs.microsoft.com/powershell/sqlserver/sqlserver/vlatest/add-sqlazureauthenticationcontext) | Yes | No
 |Step 7. Re-encrypt each value of the column encryption key, which is currently protected with the old column master key, using the new column master key. | [New-SqlColumnEncryptionKeyEncryptedValue](https://docs.microsoft.com/powershell/sqlserver/sqlserver/vlatest/new-sqlcolumnencryptionkeyencryptedvalue)<br><br>**Note:** When calling this cmdlet, pass the SqlColumnMasterKeySettings objects for both the old and the new column master key, along with a value of the column encryption key, to be re-encrypted.|Yes|No
 |Step 8. Share the location of the new column master key (the provider name and a key path of the column master key) and the set of new encrypted values of the column encryption keys, with your DBA.| See the examples below. | No | No

docs/reporting-services/install-windows/claims-to-windows-token-service-c2wts-and-reporting-services.md

@@ -45,7 +45,7 @@ If your environment will use Kerberos constrained delegation, then the SharePoin
 
     **As a best practice C2WTS should run under its own domain identity.**
 
-    * Create an Active Directory account and register the account as a managed account in SharePoint Server. To learn more about managed accounts, see [Managed Accounts in Sharepoint](https://blogs.technet.microsoft.com/wbaer/2010/04/11/managed-accounts-in-sharepoint-2010/)
+    * Create an Active Directory account and register the account as a managed account in SharePoint Server. To learn more about managed accounts, see [Managed Accounts in Sharepoint](https://blog.wbaer.net/2010/04/11/managed-accounts-in-sharepoint-2010/)
 
     * Configure C2WTS Service to use the managed account through SharePoint Central Administration > Security > Configure Service Accounts > Windows Service - Claims to Windows Token Service
 

docs/reporting-services/report-builder/exporting-to-microsoft-word-report-builder-and-ssrs.md

@@ -146,7 +146,7 @@ ms.author: maggies
 > [!IMPORTANT]  
 >  The [!INCLUDE[ofprword](../../includes/ofprword-md.md)] 2003 (.doc) rendering extension is deprecated. For more information, see [Deprecated Features in SQL Server Reporting Services in SQL Server 2016](~/reporting-services/deprecated-features-in-sql-server-reporting-services-ssrs.md).  
   
- The Word renderer is compatible with [!INCLUDE[ofprword](../../includes/ofprword-md.md)] 2003 with the [!INCLUDE[msCoName](../../includes/msconame-md.md)] Office Compatibility Pack for Word, Excel, and PowerPoint installed. For more information, see [Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint](https://go.microsoft.com/fwlink/?LinkID=205622).  
+ The Word renderer is compatible with [!INCLUDE[ofprword](../../includes/ofprword-md.md)] 2003 with the [!INCLUDE[msCoName](../../includes/msconame-md.md)] Office Compatibility Pack for Word, Excel, and PowerPoint installed. For more information, see [Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint](https://www.microsoft.com/download/details.aspx?id=12439).  
 
  The previous version of the Word rendering extension, compatible with [!INCLUDE[ofprword](../../includes/ofprword-md.md)] 2003, is renamed to Word 2003. Only the Word rendering extension is available by default. You must update the Reporting Services configuration files to make the Word 2003 rendering extension available. The content type of files generated by the Word 2003 renderer is **application/vnd.ms-word** and the file name extension of files is .doc.  
 

docs/reporting-services/report-data/oracle-connection-type-ssrs.md

@@ -16,7 +16,7 @@ To use data from an Oracle database in your report, you must you must have a dat
 
 To install the Oracle Client tools you can do the following.
 
-1.	Go to [Oracle's download site](https://www.oracle.com/us/products/tools/index-090165.html)
+1.	Go to [Oracle's download site](https://www.oracle.com/downloads/)
 2.	Download ODAC 12c Release 4 (12.1.0.2.4) for Windows (64bit for server, 32bit for tools)
 3.	Install the Data Provider for .NET 4
 

docs/sql-server/partner-monitor-sql-server.md

@@ -83,6 +83,6 @@ To learn more about some of our other partners, see [High availability and disas
 [idera_requirements]:https://www.idera.com/productssolutions/sqlserver/sqldiagnosticmanager/systemrequirements
 
 <!--LinkedIn-->
-[sentryone_linkedin]:https://www.linkedin.com/company/sentryone 
+[sentryone_linkedin]:https://www.linkedin.com/company/sentryone
 [redgate_linkedin]:https://www.linkedin.com/company/red-gate-software/
 [solarwinds_linkedin]:https://linkedin.com/showcase/solarwinds-database-performance