Add HTTPS.

Author: MikeRayMSFT

docs/integration-services/import-export-data/data-type-mapping-in-the-sql-server-import-and-export-wizard.md

@@ -29,7 +29,7 @@ The wizard uses mapping files that are installed by [!INCLUDE[ssNoVersion](../..
 If your business requires different mappings between data types, you can update the mapping files to change the mappings used by the wizard. For example, if you want the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] **nchar** data type to map to the DB2 **GRAPHIC** data type instead of the DB2 **VARGRAPHIC** data type when you transfer data from [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to DB2, you can change the **nchar** mapping in the **SqlClientToIBMDB2.xml** mapping file to use **GRAPHIC** instead of **VARGRAPHIC.**  
 
 ## You can add a new mapping file
-[!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] installs mappings between many commonly used combinations of source and destination. You can also add new mapping files to the **MappingFiles** directory to support additional sources and destinations. The new mapping files must conform to the published XSD schema and must map between a unique combination of source and destination. The schema for mapping files, **DataTypeMapping.xsd**, is published [here](http://schemas.microsoft.com/sqlserver/2008/07/IntegrationServices/DataTypeMapping/DataTypeMapping.xsd).
+[!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] installs mappings between many commonly used combinations of source and destination. You can also add new mapping files to the **MappingFiles** directory to support additional sources and destinations. The new mapping files must conform to the published XSD schema and must map between a unique combination of source and destination. The schema for mapping files, **DataTypeMapping.xsd**, is published [here](https://schemas.microsoft.com/sqlserver/2008/07/IntegrationServices/DataTypeMapping/DataTypeMapping.xsd).
 
 ## Sample mapping file
 Here's a portion of the XML mapping file that maps from SQL Server data types (or, more specifically, from the data types used by the .Net Framework Data Provider for SQL Server) to Oracle data types. As one example, you can see that a SQL Server **int** data type maps to an Oracle **INTEGER** data type.

docs/relational-databases/performance/view-and-work-with-the-output-from-the-database-engine-tuning-advisor.md

@@ -170,7 +170,7 @@ ms.author: jrasnick
     C:\Program Files\Microsoft SQL Server\100\Tools\Binn\schemas\sqlserver\2004\07\dta\dtaschema.xsd  
     ```  
   
-     The Database Engine Tuning Advisor XML schema is also available online at [http://schemas.microsoft.com/sqlserver/2004/07/dta/](http://schemas.microsoft.com/sqlserver/2004/07/dta/).  
+     The Database Engine Tuning Advisor XML schema is also available online at [https://schemas.microsoft.com/sqlserver/2004/07/dta/](https://schemas.microsoft.com/sqlserver/2004/07/dta/).  
   
 6.  After creating a workload and an XML input file, you are ready to submit the input file to the **dta** command-line utility for analysis. Make sure that you specify an XML output file name for the **-ox** utility argument. This creates an XML output file with a recommended configuration specified in the **Configuration** element. If you want to run Database Engine Tuning Advisor again to check another hypothetical configuration that is based on the output, you can copy and paste the **Configuration** element contents from the output file into a new or your original XML input file. For information about using an XML input file with the **dta** utility, see the section "Tune a Database by Using the dta Utility" in [Start and Use the Database Engine Tuning Advisor](../../relational-databases/performance/start-and-use-the-database-engine-tuning-advisor.md).