![\"SSIS](\"https:\/\/3cloudsolutions.com\/wp-content\/uploads\/2022\/11\/SSIS-in-Azure-1.png\")
\u00a0<\/span><\/strong><\/p>\nIf you\u2019ve been\u00a0avoiding\u00a0Azure\u00a0or\u00a0annoyed\u00a0that it doesn\u2019t have many of the\u00a0Microsoft\u00a0BI tools your team knows so well, this announcement is for you.<\/p>\n
If you’ve\u00a0embraced Azure Data Factory\u00a0(ADF), but loathe diving into custom activities and code for things you know you could get done quickly\u00a0in SSIS, this announcement is for you.<\/p>\n
If you\u2019ve been creating killer analytics solutions\u00a0in Azure\u00a0but struggling to get operational support from your BI team, this announcement is for you.<\/p>\n
Is it ready for my production ETL?\u00a0<\/strong><\/h2>\nNot\u00a0yet. The capabilities to support\u00a0a production\u00a0ETL are on the way.\u00a0What\u2019s missing?<\/p>\n
Deeper Integration with Azure Data Factory<\/strong>
\nWithout getting too\u00a0technical (plenty of time for that\u00a0later), SSIS in Azure is built on top of Azure Data Factory.\u00a0As of today, you can deploy packages and SSIS projects\u00a0to run as a managed Azure Service. You can\u2019t, however, execute\u00a0SSIS packages from an ADF pipeline or otherwise communicate with SSIS from ADF.<\/p>\nEnterprise and 3rd\u00a0party component support<\/strong>
\nRight\u00a0now,\u00a0only the standard SSIS components available in the SSIS Standard license are available. Use a custom component to generate hashes for dimension processing? Not supported yet. Extracting data from Dynamics and using third-party source components? Not supported\u00a0yet.<\/p>\nWhat’s available today?\u00a0\u202f\u00a0<\/strong><\/h2>\nThe feature set isn\u2019t complete, but\u00a0this release\u00a0targets the needs\u00a0of\u00a0two\u00a0<\/em>similar sets of customers:\u00a0those looking to migrate\u00a0all of\u00a0their SSIS workloads\u00a0into Azure and those looking to start deploying new\u00a0SSIS\u00a0integrations to Azure\u00a0and\u00a0maintain their existing work on-premises.<\/p>\nManaged\u00a0SSIS\u00a0in Azure\u00a0will be available in the East US and North Europe Azure data centers. The Azure-SSIS Integration Runtime\u00a0(IR)\u00a0will be available in six different sizes and support only the Standard Edition Features. The SSIS IR can be joined to a\u00a0VNet, but only one in classic mode. And during Public Preview, the\u00a0service will have 24\/7\u00a0support\u00a0to keep the service running healthy while you try it out.<\/p>\n
What\u2019s a public preview?\u00a0<\/strong><\/h2>\nYou can think of a public preview as a more advanced version of a\u00a0beta<\/a>. The service is mostly stable but the product team is still working out the kinks, completing available features and deploying new ones. The preview period of a service is the best time to start \u201ckicking the tires\u201d and getting a feel for how it might fit into your architecture.<\/p>\nThe Public Preview period is\u00a0also a great time to get to know the product teams, give them feedback and let them know what\u2019s important to you. They\u2019re looking for those passionate, early adopters to\u00a0help\u00a0drive their roadmap.<\/p>\n
\nWithout getting too\u00a0technical (plenty of time for that\u00a0later), SSIS in Azure is built on top of Azure Data Factory.\u00a0As of today, you can deploy packages and SSIS projects\u00a0to run as a managed Azure Service. You can\u2019t, however, execute\u00a0SSIS packages from an ADF pipeline or otherwise communicate with SSIS from ADF.<\/p>\n
Enterprise and 3rd\u00a0party component support<\/strong> The feature set isn\u2019t complete, but\u00a0this release\u00a0targets the needs\u00a0of\u00a0two\u00a0<\/em>similar sets of customers:\u00a0those looking to migrate\u00a0all of\u00a0their SSIS workloads\u00a0into Azure and those looking to start deploying new\u00a0SSIS\u00a0integrations to Azure\u00a0and\u00a0maintain their existing work on-premises.<\/p>\n Managed\u00a0SSIS\u00a0in Azure\u00a0will be available in the East US and North Europe Azure data centers. The Azure-SSIS Integration Runtime\u00a0(IR)\u00a0will be available in six different sizes and support only the Standard Edition Features. The SSIS IR can be joined to a\u00a0VNet, but only one in classic mode. And during Public Preview, the\u00a0service will have 24\/7\u00a0support\u00a0to keep the service running healthy while you try it out.<\/p>\n You can think of a public preview as a more advanced version of a\u00a0beta<\/a>. The service is mostly stable but the product team is still working out the kinks, completing available features and deploying new ones. The preview period of a service is the best time to start \u201ckicking the tires\u201d and getting a feel for how it might fit into your architecture.<\/p>\n The Public Preview period is\u00a0also a great time to get to know the product teams, give them feedback and let them know what\u2019s important to you. They\u2019re looking for those passionate, early adopters to\u00a0help\u00a0drive their roadmap.<\/p>\n
\nRight\u00a0now,\u00a0only the standard SSIS components available in the SSIS Standard license are available. Use a custom component to generate hashes for dimension processing? Not supported yet. Extracting data from Dynamics and using third-party source components? Not supported\u00a0yet.<\/p>\nWhat’s available today?\u00a0\u202f\u00a0<\/strong><\/h2>\n
What\u2019s a public preview?\u00a0<\/strong><\/h2>\n