|
| 1 | +--- |
| 2 | +title: "Validate SSIS packages deployed to Azure | Microsoft Docs" |
| 3 | +ms.date: "11/27/2017" |
| 4 | +ms.topic: "article" |
| 5 | +ms.prod: "sql-non-specified" |
| 6 | +ms.prod_service: "integration-services" |
| 7 | +ms.service: "" |
| 8 | +ms.component: "lift-shift" |
| 9 | +ms.suite: "sql" |
| 10 | +ms.custom: "" |
| 11 | +ms.technology: |
| 12 | + - "integration-services" |
| 13 | +author: "douglaslMS" |
| 14 | +ms.author: "douglasl" |
| 15 | +manager: "craigg" |
| 16 | +--- |
| 17 | +# Validate SSIS packages deployed to Azure |
| 18 | +When you deploy a SQL Server Integration Services (SSIS) project to the SSIS Catalog database (SSISDB) on an Azure server, the Package Deployment Wizard adds an additional validation step after the **Review** page. This validation step checks the packages in the project for known issues that may prevent the packages from running as expected in the Azure SSIS Integration Runtime. Then the wizard displays any applicable warnings on the **Validate** page. |
| 19 | + |
| 20 | +> [!IMPORTANT] |
| 21 | +> The validation described in this article occurs when you deploy a project with SQL Server Data Tools (SSDT) version 17.4 or later. To get the latest version of SSDT, see [Download SQL Server Data Tools (SSDT)](../../ssdt/download-sql-server-data-tools-ssdt.md). |
| 22 | +
|
| 23 | +For more info about the Package Deployment Wizard, see [Deploy Integration Services (SSIS) Projects and Packages](../packages/deploy-integration-services-ssis-projects-and-packages.md). |
| 24 | + |
| 25 | +## Validate connection managers |
| 26 | + |
| 27 | +The wizard checks certain connection managers for the following issues, which may cause the connection to fail: |
| 28 | +- **Windows authentication**. If a connection string uses Windows authentication, validation raises a warning. Windows authentication requires additional configuration steps. For more info, see [Connect to on-premises data sources with Windows Authentication](ssis-azure-connect-with-windows-auth.md). |
| 29 | +- **File path**. If a connection string contains a hard-coded local file path like `C:\\...`, validation raises a warning. Packages that contain an absolute path may fail. |
| 30 | +- **UNC path**. If a connection string contains a UNC pathif a connection string contains a UNC path, validation raises a warning. Packages that contain a UNC path may fail, typically because a UNC path requires Windows authentication to access. |
| 31 | +- **Host name**. If a server property contains host name instead of IP address, validation raises a warning. Packages that contain host name may fail, typically because the Azure virtual network requires the correct DNS configuration to support DNS name resolution. |
| 32 | +- **Provider or driver**. If a provider or driver is not supported, validation raises a warning. Only a small number of built-in providers and drivers are supported at this time. |
| 33 | + |
| 34 | +The wizard does the following validation checks for the connection managers in the list. |
| 35 | + |
| 36 | +| Connection Manager | Windows authentication | File path | UNC path | Host name | Provider or driver | |
| 37 | +|--------------------|----------|-----------|-----|-----------|-------------------| |
| 38 | +| Ado | ✓ | | | ✓ | ✓ | |
| 39 | +| AdoNet | ✓ | | | ✓ | ✓ | |
| 40 | +| Cache | | ✓ | ✓ | | | |
| 41 | +| Excel | | ✓ | ✓ | | | |
| 42 | +| File | | ✓ | ✓ | | | |
| 43 | +| FlatFile | | ✓ | ✓ | | | |
| 44 | +| Ftp | | | | ✓ | | |
| 45 | +| MsOLAP100 | | | | ✓ | ✓ | |
| 46 | +| MultiFile | | ✓ | ✓ | | | |
| 47 | +| MultiFlatFile | | ✓ | ✓ | | | |
| 48 | +| OData | ✓ | | | ✓ | | |
| 49 | +| Odbc | ✓ | | | ✓ | ✓ | |
| 50 | +| OleDb | ✓ | | | ✓ | ✓ | |
| 51 | +| SmoServer | ✓ | | | ✓ | | |
| 52 | +| Smtp | ✓ | | | ✓ | | |
| 53 | +| SqlMobile | | ✓ | ✓ | | | |
| 54 | +| Wmi | ✓ | | | | | |
| 55 | +||||||| |
| 56 | + |
| 57 | +## Validate sources and destinations |
| 58 | +The following third-party sources and destinations are not supported: |
| 59 | + |
| 60 | +- Oracle Source and Destination by Attunity |
| 61 | +- Teradata Source and Destination by Attunity |
| 62 | +- SAP BI Source and Destination |
| 63 | + |
| 64 | +## Validate tasks and components |
| 65 | + |
| 66 | +### Execute Process Task |
| 67 | + |
| 68 | +Validation raises a warning if a command points to a local file with an absolute path, or to a file with a UNC path. These paths may cause execution on Azure to fail. |
| 69 | + |
| 70 | +### Script Task and Script Component |
| 71 | + |
| 72 | +Validation raises a warning if a package contains a script task or a script component, which may reference or call unsupported assemblies. These references or calls may cause execution to fail. |
| 73 | + |
| 74 | +### Other components |
| 75 | + |
| 76 | +The Orc format is not supported in the HDFS Destination and the Azure Data Lake Store Destination. |
| 77 | + |
| 78 | +## Next steps |
| 79 | +To learn how to schedule package execution on Azure, see [Schedule the execution of an SSIS package on Azure](ssis-azure-schedule-packages.md). |
0 commit comments