Our SSIS IR is taking approximately 20 - 25 minutes to startup. The current setup is D8_V3 8 cores, 2 nodes, Standard with a reference to a custom DLL. Is there something that I can do to reduce the amount of time it takes to start the service? Thank you.

Hello @Paula , UPDATE: This issue has been resolved via offline communication. A hotfix is deployed to fix this issue. @Paula has confirmed, I was able to start my SSIS-IR in approximately 2 minutes today! ---------------------- By design (it takes 20-30 min) to start an SSIS IR in the VNET. 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. You can use Express custom setup provisioning can support all SSIS IRs outside a Virtual Network (VNet), with or without custom setups that can be configured following this <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fazure%2Fdata-factory%2Fhow-to-configure-azure-ssis-ir-custom-setup&data=02%7C01%7Cdashe%40microsoft.com%7Cd4764ae3d44a4daa6e8c08d6f3cc6f5c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964458011331142&sdata=hnEG2BomVmDiigBzltAs8P%2B1cc8X7%2BJ%2FvGsA2Qa%2Bbuw%3D&reserved=0" rel="ugc nofollow">documentation . Due to current technical limitations, standby VMs cannot be leveraged to shorten the provisioning time of SSIS IRs joining/inside a VNet. Reference: Express Provisioning of Azure-SSIS Integration Runtime Hope this helps. Do let us know if you any further queries. ---------------------------------------------------------------------------------------- Do click on " Accept Answer " and Upvote on the post that helps you, this can be beneficial to other community members.

Hi! I've the same issue & almost the same config. Can you help me, please?

DataFactory Integration Runtime Slow Startup

Accepted answer

PRADEEPCHEEKATLA-MSFT 89,466 Reputation points Microsoft Employee

2020-10-09T03:36:06.267+00:00

Hello @Paula ,

UPDATE: This issue has been resolved via offline communication.

A hotfix is deployed to fix this issue.

@Paula has confirmed, I was able to start my SSIS-IR in approximately 2 minutes today!

----------------------

By design (it takes 20-30 min) to start an SSIS IR in the VNET. 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.

You can use Express custom setup 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.

Reference: Express Provisioning of Azure-SSIS Integration Runtime

Hope this helps. Do let us know if you any further queries.

----------------------------------------------------------------------------------------

Do click on "Accept Answer" and Upvote on the post that helps you, this can be beneficial to other community members.
Please sign in to rate this answer.

1 person found this answer helpful.
PRADEEPCHEEKATLA-MSFT 89,466 Reputation points Microsoft Employee

2020-10-12T12:48:00.7+00:00

Hello @Paula ,

Just checking in to see if the above answer helped. If this answers your query, do click “Accept Answer” and Up-Vote for the same. And, if you have any further query do let us know.

Paula 26 Reputation points

2020-10-12T15:02:32.03+00:00

Hi,
No, I'm afraid it has not helped. The SSIS-IR was already setup using the "Express custom setup" instructions in the documentation you forwarded. We are using a custom DLL created in-house that is added to the GAC for reference by the ETL process. I also reviewed the information in the reference document "Express Provisioning of Azure-SSIS Integration Runtime" and we are not using a VNET. One of the comments in that reference article instructed the developer to open an Azure ticket, but we currently do not have a support plan so I don't think I have the ability to open a support ticket. Please let me know what else I could do to help resolve this issue.
Thank you,
Paula

PRADEEPCHEEKATLA-MSFT 89,466 Reputation points Microsoft Employee

2020-10-14T05:34:16.85+00:00

Hello @Paula ,

For a deeper investigation and immediate assistance on this issue, could you please send an email to azcommunity [at] microsoft [dot] com with the below details:

Subject of the email: <ATTN: PRADEEP - DataFactory Integration Runtime Slow Startup>

Thread URL: https://learn.microsoft.com/en-us/answers/questions/120844/datafactory-integration-runtime-slow-startup.html

Subscription ID:

Data factory name:

Region:

Please let me know here once you have done the same.

Paula 26 Reputation points

2020-10-14T12:09:25.68+00:00

Hi @PRADEEPCHEEKATLA-MSFT

I have emailed the information requested.

Thanks very much,
Paula

PRADEEPCHEEKATLA-MSFT 89,466 Reputation points Microsoft Employee

2020-10-15T05:24:38.31+00:00

Hello @Paula ,

Thanks for the sending the details.
We have forwarded those details to the product team. And I will get back to you once I hear back from them.

PRADEEPCHEEKATLA-MSFT 89,466 Reputation points Microsoft Employee

2020-10-21T04:18:34.533+00:00

Hello @Paula ,

This issue has been resolved via offline communication.

A hotfix is deployed to fix this issue.

@Paula has confirmed, I was able to start my SSIS-IR in approximately 2 minutes today!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

DataFactory Integration Runtime Slow Startup

1 additional answer

Your answer