|
| 1 | +--- |
| 2 | +title: On-premises SQL Server Integration Services (SSIS) workloads to SSIS in Azure Data Factory (ADF) or Synapse Pipelines migration rules |
| 3 | +description: SSIS workloads migration assessment rules. |
| 4 | +author: chugugrace |
| 5 | +ms.author: chugu |
| 6 | +ms.service: data-factory |
| 7 | +ms.subservice: integration-services |
| 8 | +ms.topic: conceptual |
| 9 | +ms.date: 07/07/2022 |
| 10 | +--- |
| 11 | + |
| 12 | +# SSIS migration assessment rules |
| 13 | + |
| 14 | +[!INCLUDE[appliesto-adf-asa-preview-md](includes/appliesto-adf-asa-preview-md.md)] |
| 15 | + |
| 16 | +When planning a migration of on-premises SSIS to SSIS in Azure Data Factory (ADF) or Synapse Pipelines, assessment will help identify issues with the source SSIS packages that would prevent a successful migration. |
| 17 | + |
| 18 | +[Data Migration Assistant (DMA) for Integration Services](/sql/dma/dma-assess-ssis) can perform assessment of your project, and below are full list of potential issues, known as DMA rules as well. |
| 19 | + |
| 20 | +### [1001]Connection with host name may fail |
| 21 | + |
| 22 | +**Impact** |
| 23 | + |
| 24 | +Connection that contains host name may fail, typically because the Azure virtual network requires the correct configuration to support DNS name resolution.</Impact> |
| 25 | + |
| 26 | +**Recommendation** |
| 27 | + |
| 28 | +You can use below options for SSIS Integration runtime to access these resources: |
| 29 | + |
| 30 | +- [Join Azure-SSIS IR to a virtual network that connects to on-premise sources](/azure/data-factory/join-azure-ssis-integration-runtime-virtual-network) |
| 31 | +- Migrate your data to Azure and use Azure resource endpoint. |
| 32 | +- Use Managed Identity authentication if moving to Azure resources. |
| 33 | +- [Use self-hosted IR to connect on-premise sources](/azure/data-factory/self-hosted-integration-runtime-proxy-ssis). |
| 34 | + |
| 35 | +### [1002]Connection with absolute or UNC path might not be accessible |
| 36 | + |
| 37 | +Impact |
| 38 | + |
| 39 | +Connection that contains absolute or UNC path may fail |
| 40 | + |
| 41 | +Recommendation |
| 42 | + |
| 43 | +You can use below options for SSIS Integration runtime to access these resources: |
| 44 | + |
| 45 | +- [Change to %TEMP%](/azure/data-factory/ssis-azure-files-file-shares) |
| 46 | +- [Migrate your files to Azure Files](/azure/data-factory/ssis-azure-files-file-shares) |
| 47 | +- [Join Azure-SSIS IR to a virtual network that connects to on-premise sources](/azure/data-factory/join-azure-ssis-integration-runtime-virtual-network). |
| 48 | +- [Use self-hosted IR to connect on-premise sources](/azure/data-factory/self-hosted-integration-runtime-proxy-ssis). |
| 49 | + |
| 50 | +### [1003]Connection with Windows authentication may fail |
| 51 | + |
| 52 | +Impact |
| 53 | + |
| 54 | +If a connection string uses Windows authentication, it may fail. Windows authentication requires additional configuration steps in Azure. |
| 55 | + |
| 56 | +Recommendation |
| 57 | + |
| 58 | +There are [four methods to access data stores Windows authentication in Azure SSIS integration runtime](/sql/integration-services/lift-shift/ssis-azure-connect-with-windows-auth): |
| 59 | + |
| 60 | +- Set up an activity-level execution context |
| 61 | +- Set up a catalog-level execution context |
| 62 | +- Persist credentials via cmdkey command |
| 63 | +- Mount drives at package execution time (non-persistent) |
| 64 | + |
| 65 | +### [1004]Connection with non built-in provider or driver may fail |
| 66 | + |
| 67 | +Impact |
| 68 | + |
| 69 | +Azure-SSIS IR only includes built-in providers or drivers by default. Without customization to install the provider or driver, the connection may fail. |
| 70 | + |
| 71 | +Recommendation |
| 72 | + |
| 73 | +[Customize Azure-SSIS integration runtime](/azure/data-factory/how-to-configure-azure-ssis-ir-custom-setup) to install non built-in provider or driver. |
| 74 | + |
| 75 | +### [1005]Analysis Services Connection Manager cannot use an account with MFA enabled |
| 76 | + |
| 77 | +Impact |
| 78 | + |
| 79 | +If you use SSIS in Azure Data Factory (ADF) and want to connect to Azure Analysis Services (AAS) instance, you cannot use an account with Multi-Factor Authentication (MFA) enabled. |
| 80 | + |
| 81 | +Recommendation |
| 82 | + |
| 83 | +Use an account that doesn't require any interactivity/MFA or a service principal instead. |
| 84 | + |
| 85 | +AdditionalInformation |
| 86 | + |
| 87 | +[Configuration of the Analysis Services Connection Manager](/sql/integration-services/connection-manager/analysis-services-connection-manager) |
| 88 | + |
| 89 | +### [1006]Windows environment variable in Connection Manager is discovered |
| 90 | + |
| 91 | +Impact |
| 92 | + |
| 93 | +Connection Manager using Windows environment variable is discovered. |
| 94 | + |
| 95 | +Recommendation |
| 96 | + |
| 97 | +You can use below methods to have Windows environment variables working in SSIS Integration runtime: |
| 98 | + |
| 99 | +- [Customize SSIS integration runtime setup](/azure/data-factory/how-to-configure-azure-ssis-ir-custom-setup) with Windows environment variables. |
| 100 | +- [Use Package or Project Parameter](/sql/integration-services/integration-services-ssis-package-and-project-parameters). |
| 101 | + |
| 102 | +### [1007]SQL Server Native Client (SNAC) OLE DB driver is deprecated |
| 103 | + |
| 104 | +Recommendation |
| 105 | + |
| 106 | +[Use latest Microsoft OLE DB Driver](/sql/connect/oledb/oledb-driver-for-sql-server) |
| 107 | + |
| 108 | +### [2001]Component only supported in enterprise edition |
| 109 | + |
| 110 | +Impact |
| 111 | + |
| 112 | +The component is only supported in Azure SSIS integration runtime enterprise edition. |
| 113 | + |
| 114 | +Recommendation |
| 115 | + |
| 116 | +[Configure Azure SSIS integration runtime to enterprise edition](/azure/data-factory/how-to-configure-azure-ssis-ir-enterprise-edition). |
| 117 | + |
| 118 | +### [2002]ORC and Parquet file format aren't by default enabled |
| 119 | + |
| 120 | +Impact |
| 121 | + |
| 122 | +ORC and Parquet file format need JRE, which isn't by default installed in Azure SSIS integration runtime.</Impact> |
| 123 | + |
| 124 | +Recommendation |
| 125 | + |
| 126 | +Install compatible JRE by [customize setup for the Azure-SSIS integration runtime](/azure/data-factory/how-to-configure-azure-ssis-ir-custom-setup). |
| 127 | + |
| 128 | +### [2003]Third party component isn't by default enabled |
| 129 | + |
| 130 | +Impact |
| 131 | + |
| 132 | +Azure SSIS Integration Runtime isn't by default enabled with third party components. Third party component may fail. |
| 133 | + |
| 134 | +Recommendation |
| 135 | + |
| 136 | +- Contact the third party to get an SSIS Integration runtime compatible version. |
| 137 | + |
| 138 | +- For in-house or open source component, [customize Azure-SSIS integration runtime](/azure/data-factory/how-to-configure-azure-ssis-ir-custom-setup) to install necessary SQL Server 2017 compatible components. |
| 139 | + |
| 140 | +### [2004]Azure Blob source and destination is discovered |
| 141 | + |
| 142 | +Recommendation |
| 143 | + |
| 144 | +Recommend to use [Flexible File source](/sql/integration-services/data-flow/flexible-file-source) or [destination](/sql/integration-services/data-flow/flexible-file-destination), which has more advanced functions than Azure Blob. |
| 145 | + |
| 146 | +### [2005]Non built-in log provider may not be installed by default |
| 147 | + |
| 148 | +Impact |
| 149 | + |
| 150 | +Azure SSIS integration time is provisioned with built-in log providers by default only, customize log provider may fail. |
| 151 | + |
| 152 | +Recommendation |
| 153 | + |
| 154 | +[Customize Azure-SSIS integration runtime](/azure/data-factory/how-to-configure-azure-ssis-ir-custom-setup) to install non built-in provider or driver. |
| 155 | + |
| 156 | +### [3001]Absolute or UNC path is discovered in Execute Process Task |
| 157 | + |
| 158 | +Impact |
| 159 | + |
| 160 | +Azure-SSIS Integration Runtime might not be able to launch your executable(s) with absolute or UNC path.</Impact> |
| 161 | + |
| 162 | +Recommendation |
| 163 | + |
| 164 | +You can use below options for SSIS Integration runtime to launch your executable(s): |
| 165 | + |
| 166 | +- [Migrate your executable(s) to Azure Files](/azure/data-factory/ssis-azure-files-file-shares). |
| 167 | +- [Join Azure-SSIS IR to a virtual network](/azure/data-factory/join-azure-ssis-integration-runtime-virtual-network) that connects to on-premise sources. |
| 168 | +- If necessary, [customize setup script to install your executable(s)](/azure/data-factory/how-to-configure-azure-ssis-ir-custom-setup) in advance when starting IR. |
| 169 | + |
| 170 | +### [4001]Absolute or UNC configuration path is discovered in package configuration |
| 171 | + |
| 172 | +Impact |
| 173 | + |
| 174 | +Package with absolute or UNC configuration path may fail in Azure SSIS Integration Runtime. |
| 175 | + |
| 176 | +Recommendation |
| 177 | + |
| 178 | +You can use below options for SSIS Integration runtime to access these resources: |
| 179 | + |
| 180 | +- [Migrate your files to Azure Files](/azure/data-factory/ssis-azure-files-file-shares) |
| 181 | +- [Join Azure-SSIS IR to a virtual network that connects to on-premise sources](/azure/data-factory/join-azure-ssis-integration-runtime-virtual-network). |
| 182 | +- [Use self-hosted IR to connect on-premise sources](/azure/data-factory/self-hosted-integration-runtime-proxy-ssis). |
| 183 | + |
| 184 | +### [4002]Registry entry is discovered in package configuration |
| 185 | + |
| 186 | +Impact |
| 187 | + |
| 188 | +Registry entry in package configuration may fail in Azure SSIS Integration Runtime. |
| 189 | + |
| 190 | +Recommendation |
| 191 | + |
| 192 | +Use other package configuration types. XML configuration file is recommended. |
| 193 | + |
| 194 | +Additional Information |
| 195 | + |
| 196 | +[Package Configurations](/sql/integration-services/package-configurations) |
| 197 | + |
| 198 | +### [4003]Package encrypted with user key isn't supported |
| 199 | + |
| 200 | +Impact |
| 201 | + |
| 202 | +Package encrypted with user key isn't supported in Azure SSIS Integration Runtime. |
| 203 | + |
| 204 | +Recommendation |
| 205 | + |
| 206 | +You can use below options: |
| 207 | + |
| 208 | +- Change the package protection level to "Encrypt All With Password" or "Encrypt Sensitive With Password". |
| 209 | +- Keep or change the package protection level to "Encrypt Sensitive With User Key", override connection manager property during package execution |
| 210 | + |
| 211 | +Additional Information |
| 212 | + |
| 213 | +[Access Control for Sensitive Data in Packages](/sql/integration-services/security/access-control-for-sensitive-data-in-packages) |
0 commit comments