Merge pull request #4153 from MicrosoftDocs/master

11/30 PM Publish

Author: v-alje

docs/connect/odbc/linux-mac/programming-guidelines.md

@@ -71,21 +71,36 @@ The following features are not available in this release of the ODBC driver on m
 
 ## Character Set Support
 
-The client encoding can be one of the following:
+SQLCHAR data in one of the following character sets is supported by the driver:
+
   -  UTF-8
-  -  ISO-8859-1
-  -  ISO-8859-2
+  -  CP437
+  -  CP850
+  -  CP874
+  -  CP932
+  -  CP936
+  -  CP949
+  -  CP950
+  -  CP1251
+  -  CP1253
+  -  CP1256
+  -  CP1257
+  -  CP1258
+  -  ISO-8859-1 / CP1252
+  -  ISO-8859-2 / CP1250
   -  ISO-8859-3
   -  ISO-8859-4
   -  ISO-8859-5
   -  ISO-8859-6
   -  ISO-8859-7
-  -  ISO-8859-8
-  -  ISO-8859-9
+  -  ISO-8859-8 / CP1255
+  -  ISO-8859-9 / CP1254
   -  ISO-8859-13
   -  ISO-8859-15
-  
-SQLCHAR data must be one of the supported character sets. SQLWCHAR data must be UTF-16LE (Little Endian).  
+
+Upon connection, the driver detects the current locale of the process it is loaded in. If it is one of the supported encodings above, the driver will use that encoding for SQLCHAR (narrow-character) data; otherwise, it defaults to UTF-8. Since all processes start in the "C" locale by default (and thus cause the driver to default to UTF-8), if an application needs to use one of the encodings above, it should use the **setlocale** function to set the locale appropriately before connecting; either by specifying the desired locale explicitly, or using an empty string e.g. `setlocale(LC_ALL, "")`, to use the locale settings of the environment.
+
+SQLWCHAR data must be UTF-16LE (Little Endian).
 
 If SQLDescribeParameter does not specify a SQL type on the server, the driver uses the SQL type specified in the *ParameterType* parameter of SQLBindParameter. If a narrow character SQL type, such as SQL_VARCHAR, is specified in SQLBindParameter, the driver converts the supplied data from the client code page to the default [!INCLUDE[ssNoVersion](../../../includes/ssnoversion_md.md)] code page. (The default [!INCLUDE[ssNoVersion](../../../includes/ssnoversion_md.md)] code page is typically 1252.) If the client code page is not supported, it will be set to UTF-8. In this case, the driver then converts the UTF-8 data to the default code page. However, data loss is possible. If code page 1252 cannot represent a character, the driver converts the character to a question mark ('?'). To avoid this data loss, specify a Unicode SQL character type, such as SQL_NVARCHAR, in SQLBindParameter. In this case, the driver converts the supplied Unicode data in UTF-8 encoding to UTF-16 without loss of data.
 

docs/integration-services/TOC.md

@@ -177,7 +177,7 @@
 ## Follow the blog
 ### [SSIS team blog](https://blogs.msdn.microsoft.com/ssis/)
 ## Get help
-### [SSIS forum on MSDN](https://social.msdn.microsoft.com/Forums/en-us/home?forum=sqlintegrationservices)
+### [SSIS forum on MSDN](https://social.msdn.microsoft.com/Forums/home?forum=sqlintegrationservices)
 ### [SSIS tag on Stack Overflow](http://stackoverflow.com/questions/tagged/ssis)  
 ## Give feedback
 ### [Microsoft Connect](https://connect.microsoft.com/SQLServer/Feedback)  

docs/integration-services/connection-manager/azure-data-lake-store-connection-manager.md

@@ -44,15 +44,15 @@ The Azure Data Lake Store connection manager is a component of the [SQL Server I
     1.  If you select the **Azure AD User Identity** authentication option, do the following things:
         1. Provide values for the **User Name** and **Password** fields. 
 
-        2. To test the connection, select **Test Connection**. If you or the tenant administrator didn't previously consent to allow SSIS to access your Azure Data Lake Store data, select **Accept** when prompted. For more information about this consent experience, see [Integrating applications with Azure Active Directory](https://docs.microsoft.com/en-us/azure/active-directory/active-directory-integrating-applications#updating-an-application).
+        2. To test the connection, select **Test Connection**. If you or the tenant administrator didn't previously consent to allow SSIS to access your Azure Data Lake Store data, select **Accept** when prompted. For more information about this consent experience, see [Integrating applications with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-integrating-applications#updating-an-application).
 
         >   [!NOTE] 
         > When you select the **Azure AD User Identity** authentication option, multi-factor authentication and Microsoft account authentication are not supported.
     
     2. If you select the **Azure AD Service Identity** authentication option, do the following things:
         1. Create an Azure Active Directory (AAD) application and service principal to access the Azure Data Lake data.
 
-        2. Assign appropriate permissions to let this AAD application access your Azure Data Lake resources. For more information about this authentication option, see [Use portal to create Active Directory application and service principal that can access resources](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal).
+        2. Assign appropriate permissions to let this AAD application access your Azure Data Lake resources. For more information about this authentication option, see [Use portal to create Active Directory application and service principal that can access resources](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-create-service-principal-portal).
 
         3. Provide values for the **Client Id**, **Secret Key**, and **Tenant Name** fields.
 

docs/integration-services/connection-manager/azure-resource-manager-connection-manager.md

@@ -23,13 +23,13 @@ manager: "jhubbard"
 ms.workload: "Inactive"
 ---
 # Azure Resource Manager Connection Manager
-The **Azure Resource Manager Connection Manager** enables an SSIS package to manage Azure resources using a [service principal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal).
+The **Azure Resource Manager Connection Manager** enables an SSIS package to manage Azure resources using a [service principal](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-create-service-principal-portal).
 
 The **Azure Resource Manager Connection Manager** is a component of the [SQL Server Integration Services (SSIS) Feature Pack for Azure](../../integration-services/azure-feature-pack-for-integration-services-ssis.md).
 
 To create and configure an **Azure Resource Manager Connection Manager**, follow the steps below:
 
 1. In the **Add SSIS Connection Manager** dialog box, select **AzureResourceManager**, and click **Add**.
-2. In the **Azure Resource Manager Connection Manager Editor** dialog box, specify the **Application ID**, **Application Key**, and **Tenant ID** for the service principal. For details about these properties, please refer to [this](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal) article.
+2. In the **Azure Resource Manager Connection Manager Editor** dialog box, specify the **Application ID**, **Application Key**, and **Tenant ID** for the service principal. For details about these properties, please refer to [this](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-create-service-principal-portal) article.
 3. Click **OK** to close the dialog box.
 4. You can see the properties of the connection manager you created in the **Properties** window.

docs/integration-services/control-flow/azure-hdinsight-create-cluster-task.md

@@ -29,7 +29,7 @@ The **Azure HDInsight Create Cluster Task** is a component of the [SQL Server In
 
 > [!NOTE]  
 > - Creating a new HDInsight cluster may take 10~20 minutes.  
-> - There is a cost associated with creating and running an Azure HDInsight cluster. See [HDInsight Pricing](http://azure.microsoft.com/en-us/pricing/details/hdinsight/) for details.  
+> - There is a cost associated with creating and running an Azure HDInsight cluster. See [HDInsight Pricing](http://azure.microsoft.com/pricing/details/hdinsight/) for details.  
   
 To add an **Azure HDInsight Create Cluster Task**, drag-drop it to the SSIS Designer, and double-click or right-click and click **Edit** to see the following **Azure HDInsight Create Cluster Task Editor** dialog box.  
 

docs/integration-services/lesson-1-1-creating-a-new-integration-services-project.md

@@ -29,7 +29,7 @@ The packages that you will create in this [!INCLUDE[ssISnoversion](../includes/s
 > [!NOTE]  
 > This tutorial requires Microsoft SQL Server Data Tools.  
 >   
-> For more information on installing the SQL Server Data Tools see [SQL Server Data Tools Download](http://msdn.microsoft.com/en-us/data/hh297027).  
+> For more information on installing the SQL Server Data Tools see [SQL Server Data Tools Download](http://msdn.microsoft.com/data/hh297027).  
   
 ### To create a new Integration Services project  
 

docs/integration-services/lesson-1-create-a-project-and-basic-package-with-ssis.md

@@ -23,7 +23,7 @@ ms.workload: "Active"
 ---
 # Lesson 1: Create a Project and Basic Package with SSIS
 
- > For content related to previous versions of SQL Server, see [Lesson 1: Creating the Project and Basic Package](https://msdn.microsoft.com/en-US/library/ms170419(SQL.120).aspx).
+ > For content related to previous versions of SQL Server, see [Lesson 1: Creating the Project and Basic Package](https://msdn.microsoft.com/library/ms170419(SQL.120).aspx).
 
 In this lesson, you will create a simple ETL package that extracts data from a single flat file source, transforms the data using two lookup transformation components, and writes that data to the **FactCurrency** fact table in **AdventureWorksDW2012**. As part of this lesson, you will learn how to create new packages, add and configure data source and destination connections, and work with new control flow and data flow components.  
 
@@ -33,7 +33,7 @@ In this lesson, you will create a simple ETL package that extracts data from a s
 ## Understanding the Package Requirements  
 This tutorial requires Microsoft SQL Server Data Tools.  
 
-For more information on installing the SQL Server Data Tools see [SQL Server Data Tools Download](http://msdn.microsoft.com/en-us/data/hh297027).  
+For more information on installing the SQL Server Data Tools see [SQL Server Data Tools Download](http://msdn.microsoft.com/data/hh297027).  
 
 Before creating a package, you need a good understanding of the formatting used in both the source data and the destination. Once you understand both of these data formats, you will be ready to define the transformations necessary to map the source data to the destination.  
 

docs/integration-services/lesson-6-using-parameters-with-the-project-deployment-model-in-ssis.md

@@ -31,7 +31,7 @@ Using the Integration Services Project Configuration Wizard, you will convert th
 When you run the package again, the Integration Services service uses the parameter to populate the value of the variable, and the variable in turn updates the Directory property. As a result, the package iterates through the files in the new data folder specified by the parameter value rather than the folder that was set in the package configuration file.  
 
 > [!IMPORTANT]  
-> This tutorial requires the **AdventureWorksDW2012** sample database. For more information about how to install and deploy **AdventureWorksDW2012**, see [Considerations for Installing SQL Server Samples and Sample Databases](http://technet.microsoft.com/en-us/library/ms161556%28v=sql.105%29).  
+> This tutorial requires the **AdventureWorksDW2012** sample database. For more information about how to install and deploy **AdventureWorksDW2012**, see [Considerations for Installing SQL Server Samples and Sample Databases](http://technet.microsoft.com/library/ms161556%28v=sql.105%29).  
   
 ## Lesson Tasks  
 This lesson contains the following tasks:  

docs/integration-services/service/ssis-catalog.md

@@ -195,7 +195,7 @@ To run the **SSIS Server Maintenance Job**, SSIS creates the SQL Server login **
 
 -   For a project, use the **Permissions** page in the [Project Properties Dialog Box](../../integration-services/service/project-properties-dialog-box.md).  
 
--   For an environment, use the **Permissions** page in the [NIB: Environment Properties Dialog Box](http://msdn.microsoft.com/en-us/6a91a8d4-0006-4cfd-9759-3e4295ae452b).  
+-   For an environment, use the **Permissions** page in the [NIB: Environment Properties Dialog Box](http://msdn.microsoft.com/6a91a8d4-0006-4cfd-9759-3e4295ae452b).  
 
  To manage permissions using Transact-SQL, call [catalog.grant_permission (SSISDB Database)](../../integration-services/system-stored-procedures/catalog-grant-permission-ssisdb-database.md), [catalog.deny_permission (SSISDB Database)](../../integration-services/system-stored-procedures/catalog-deny-permission-ssisdb-database.md), and [catalog.revoke_permission (SSISDB Database)](../../integration-services/system-stored-procedures/catalog-revoke-permission-ssisdb-database.md). To view effective permissions for the current principal for all objects, query [catalog.effective_object_permissions (SSISDB Database)](../../integration-services/system-views/catalog-effective-object-permissions-ssisdb-database.md). This topic provides descriptions of the different types of permissions. To view permissions that have been explicitly assigned to the user, query [catalog.explicit_object_permissions (SSISDB Database)](../../integration-services/system-views/catalog-explicit-object-permissions-ssisdb-database.md).  
 

docs/integration-services/sql-server-integration-services.md

@@ -31,7 +31,7 @@ ms.workload: "Active"
 ---
 # SQL Server Integration Services
 
- > For content related to previous versions of SQL Server, see [SQL Server Integration Services](https://msdn.microsoft.com/en-US/library/ms141026(SQL.120).aspx).
+ > For content related to previous versions of SQL Server, see [SQL Server Integration Services](https://msdn.microsoft.com/library/ms141026(SQL.120).aspx).
 
 [!INCLUDE[msCoName](../includes/msconame-md.md)] [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] is a platform for building enterprise-level data integration and data transformations solutions. You use [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] to solve complex business problems by copying or downloading files, sending e-mail messages in response to events, updating data warehouses, cleaning and mining data, and managing [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] objects and data. The packages can work alone or in concert with other packages to address complex business needs. [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] can extract and transform data from a wide variety of sources such as XML data files, flat files, and relational data sources, and then load the data into one or more destinations.<br /><br /> [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] includes a rich set of built-in tasks and transformations; tools for constructing packages; and the [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] service for running and managing packages. You can use the graphical [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] tools to create solutions without writing a single line of code; or you can program the extensive [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] object model to create packages programmatically and code custom tasks and other package objects.
 
@@ -42,8 +42,8 @@ ms.workload: "Active"
 
 ##  ![info_tip](../sql-server/media/info-tip.png) Get Help
 
-- [MSDN forum for SSIS - ask questions](https://social.msdn.microsoft.com/Forums/en-us/home?forum=sqlintegrationservices)
-- [MSDN forum for SSDT and SSMS - ask questions](https://social.msdn.microsoft.com/Forums/en-US/home?forum=sqltool)
+- [MSDN forum for SSIS - ask questions](https://social.msdn.microsoft.com/Forums/home?forum=sqlintegrationservices)
+- [MSDN forum for SSDT and SSMS - ask questions](https://social.msdn.microsoft.com/Forums/home?forum=sqltool)
 - [Stack Overflow (tag *ssis*) - ask questions](http://stackoverflow.com/questions/tagged/ssis)
 - [Microsoft Connect - report bugs and request features](https://connect.microsoft.com/SQLServer/Feedback)
 - [Reddit - general discussion about SSIS](https://www.reddit.com/r/SQLServer/search?q=ssis&restrict_sr=on)