Home
%3CLINGO-SUB%20id%3D%22lingo-sub-719058%22%20slang%3D%22en-US%22%3EExpress%20Provisioning%20of%20Azure-SSIS%20Integration%20Runtime%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-719058%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20we%20continue%20to%20improve%20customer%20experience%20in%20using%20Azure-SSIS%20Integration%20Runtime%20(SSIS%20IR)%2C%20we%20are%20excited%20to%20announce%20that%20SSIS%20IR%20can%20now%20be%20provisioned%20within%205%20minutes!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20the%20past%2C%20provisioning%20SSIS%20IR%20took%20at%20least%2020-30%20minutes.%26nbsp%3B%20This%20is%20because%20the%20underlying%20nodes%2FVirtual%20Machines%20(VMs)%20would%20have%20to%20be%20created%20and%20prepared%20just%20in%20time%20from%20scratch%2C%20leading%20to%20the%20prolonged%2020-30%20minutes%20duration.%20%26nbsp%3B%26nbsp%3BThis%20has%20been%20a%20customer%20pain%20point%2C%20especially%20when%20demoing%2Ftrying%20out%20SSIS%20IR%20as%20a%20Proof%20of%20Concept%20(PoC)%20that%20needs%20to%20be%20done%20quickly.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENow%20SSIS%20IR%20creation%20can%20leverage%20pools%20of%20standby%20VMs%20that%20have%20been%20created%20and%20prepared%20in%20advance.%26nbsp%3B%20The%20standby%20VM%20types%20and%20quantities%20are%20chosen%20based%20on%20historical%20data.%26nbsp%3B%20When%20there%20is%20a%20provisioning%20request%20for%20SSIS%20IR%2C%20its%20VMs%20are%20allocated%20from%20a%20pool%20of%20standby%20VMs.%26nbsp%3B%20As%20a%20result%2C%20the%20provisioning%20time%20is%20now%20reduced%20by%20around%2080%25.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAt%20present%2C%20our%20express%20provisioning%20can%20support%20all%20SSIS%20IRs%20outside%20a%20Virtual%20Network%20(VNet)%2C%20with%20or%20without%20custom%20setups%20that%20can%20be%20configured%20following%20this%20%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fazure%252Fdata-factory%252Fhow-to-configure-azure-ssis-ir-custom-setup%26amp%3Bdata%3D02%257C01%257Cdashe%2540microsoft.com%257Cd4764ae3d44a4daa6e8c08d6f3cc6f5c%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C636964458011331142%26amp%3Bsdata%3DhnEG2BomVmDiigBzltAs8P%252B1cc8X7%252BJ%252FvGsA2Qa%252Bbuw%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edocumentation%3C%2FA%3E.%26nbsp%3B%20Due%20to%20current%20technical%20limitations%2C%20standby%20VMs%20cannot%20be%20leveraged%20to%20shorten%20the%20provisioning%20time%20of%20SSIS%20IRs%20joining%2Finside%20a%20VNet.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBased%20on%20our%20recent%20monitoring%2C%20more%20than%2095%25%20of%20SSIS%20IR%20creations%20outside%20a%20VNet%20have%20benefited%20from%20our%20express%20provisioning%20and%20excluding%20any%20custom%20setup%20time%2C%20more%20than%2095%25%20of%20them%20have%20been%20provisioned%20in%20under%205%20minutes.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20hope%20you%20will%20find%20this%20improvement%20useful.%26nbsp%3B%20Please%20do%20not%20hesitate%20to%20contact%20us%20if%20you%20have%20any%20feedbacks%2Fquestions%2Fissues%20and%20we%20will%20follow%20up%20ASAP.%26nbsp%3B%20Thank%20you%20as%20always%20for%20your%20support.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-723582%22%20slang%3D%22en-US%22%3ERe%3A%20Express%20Provisioning%20of%20Azure-SSIS%20Integration%20Runtime%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-723582%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20great%20news%2C%20is%20this%20going%20to%20work%20all%20types%20of%20VM's%20or%20only%20for%20a%20subset%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-724632%22%20slang%3D%22en-US%22%3ERe%3A%20Express%20Provisioning%20of%20Azure-SSIS%20Integration%20Runtime%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-724632%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F296550%22%20target%3D%22_blank%22%3E%40edkreuk72%3C%2FA%3E%26nbsp%3BAll%20VM%20size%20are%20supported%2C%20we%20reserved%20VM%20size%20and%20the%20number%20of%20VM%20based%20on%20history%20data%2C%20VM%20size%20and%20the%20number%20of%20VM%20is%20also%20keeping%20adjusted%20based%20on%20usage.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-985124%22%20slang%3D%22en-US%22%3ERe%3A%20Express%20Provisioning%20of%20Azure-SSIS%20Integration%20Runtime%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-985124%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20I%20started%20a%20runtime%20service%2C%20and%20it's%20taken%20between%2020%20and%2030%20minutes.%3C%2FP%3E%3CP%3EWhat%20am%20I%20doing%20wrong%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-985965%22%20slang%3D%22en-US%22%3ERe%3A%20Express%20Provisioning%20of%20Azure-SSIS%20Integration%20Runtime%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-985965%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F445381%22%20target%3D%22_blank%22%3E%40Michelon777%3C%2FA%3E%26nbsp%3BDo%20you%20use%20vNet%3F%20We%20do%20not%20support%20express%20provision%20for%20IR%20with%20vNet.%20Also%20express%20provision%20hit%20rate%20is%2095%25%2B%2C%20but%20there%20is%20some%20chance%20some%20provision%20cannot%20benefit%20express%20provision%2C%20we%20are%20continuing%20improve%20the%20algorithm%20to%20try%20achieve%20higher%20hit%20rate.%20If%20you%20can%20send%20me%20the%20subscription%20ID%2F%20data%20factory%20name%2FIR%20name%2C%20I%20can%20check%20from%20backend%20why%20your%20IR%20is%20not%20benefit%20from%20express%20provision.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

As we continue to improve customer experience in using Azure-SSIS Integration Runtime (SSIS IR), we are excited to announce that SSIS IR can now be provisioned within 5 minutes!

 

In the past, provisioning SSIS IR took at least 20-30 minutes.  This is because the underlying nodes/Virtual Machines (VMs) would have to be created and prepared just in time from scratch, leading to the prolonged 20-30 minutes duration.   This has been a customer pain point, especially when demoing/trying out SSIS IR as a Proof of Concept (PoC) that needs to be done quickly.

 

Now SSIS IR creation can leverage pools of standby VMs that have been created and prepared in advance.  The standby VM types and quantities are chosen based on historical data.  When there is a provisioning request for SSIS IR, its VMs are allocated from a pool of standby VMs.  As a result, the provisioning time is now reduced by around 80%.

 

At present, our express provisioning can support all SSIS IRs outside a Virtual Network (VNet), with or without custom setups that can be configured following this documentation.  Due to current technical limitations, standby VMs cannot be leveraged to shorten the provisioning time of SSIS IRs joining/inside a VNet.

 

Based on our recent monitoring, more than 95% of SSIS IR creations outside a VNet have benefited from our express provisioning and excluding any custom setup time, more than 95% of them have been provisioned in under 5 minutes.

 

We hope you will find this improvement useful.  Please do not hesitate to contact us if you have any feedbacks/questions/issues and we will follow up ASAP.  Thank you as always for your support.

4 Comments
Regular Visitor

Hi,

 

This is great news, is this going to work all types of VM's or only for a subset?

Microsoft

@edkreuk72 All VM size are supported, we reserved VM size and the number of VM based on history data, VM size and the number of VM is also keeping adjusted based on usage.

Frequent Visitor

Today I started a runtime service, and it's taken between 20 and 30 minutes.

What am I doing wrong?

Occasional Visitor

@Michelon777 Do you use vNet? We do not support express provision for IR with vNet. Also express provision hit rate is 95%+, but there is some chance some provision cannot benefit express provision, we are continuing improve the algorithm to try achieve higher hit rate. If you can send me the subscription ID/ data factory name/IR name, I can check from backend why your IR is not benefit from express provision.