Cloned Data Factory with SSIS Integration Runtime

Question

Cloned Data Factory with SSIS Integration Runtime

DataPeps2023 25

My company currently has ADF set up in a region that is no longer appropriate, also, 2 teams are using the same factory and we have decided to split it to 2 ADF's.

What I want to do is use DevOps from the current ADF and clone it to a new ADF - which I did a while back, but it didn't create the SSIS Integration Runtime. When I try to create a new SSIS IR, it will not allow me to create a second SSISDB on the same database.

So my question is, how to I set up the new ADF and test it without turning off / deleting the SSIS IR on the current ADF?

Smaran Thoomu 32,775 Reputation points Microsoft External Staff Moderator

2023-12-13T13:47:37.0666667+00:00
Hi @DataPeps2023

Welcome to Microsoft Q&A Platform. Thank you for posting your query.
To clone an existing Azure Data Factory (ADF) to a new ADF, you can use the Azure Portal or Azure PowerShell. However, when you clone an ADF, it doesn't include the SSIS Integration Runtime (IR) by default. You need to create a new SSIS IR in the new ADF and configure it to use the same SSISDB as the existing SSIS IR.

To create a new SSIS IR in the new ADF, follow these steps:

In the Azure Portal, navigate to the new ADF.

Click on the "Author & Monitor" button to open the ADF UI.

Click on the "Manage" tab and then click on "Integration Runtimes".

Click on the "New" button to create a new SSIS IR.

Follow the prompts to create the new SSIS IR. When prompted for the SSISDB, select "Use existing SSISDB" and enter the connection string for the existing SSISDB.

Once you have created the new SSIS IR, you can test it by creating a new pipeline that uses the SSIS IR. You can also use the "Test Connection" button in the SSIS IR settings to verify that the connection to the SSISDB is working.

Regarding the issue of not being able to create a second SSISDB on the same database, this is a limitation of SQL Server. You can only have one SSISDB per SQL Server instance. However, you can use the same SSISDB for multiple SSIS IRs in different ADFs as long as they are in the same region.

I hope this helps! Let me know if you have any further questions.
DataPeps2023 25 Reputation points

2023-12-13T15:43:54.76+00:00

Hi, thanks for taking the time to respond.

Unfortunately I don't have the option of "Use existing SSISDB" as per your suggestion in point 5. Based on your last point, I imagine it is because the current ADF is in a different region to the new one (which is part of the reason I am creating a new ADF).

I am wondering if the best option is to choose to "use package stores to manage you packages into file system...." Although I've not used this setup before and am unsure at this time how it will change how I deploy changes, or running packages. I was not looking to make any significant changes to the ADF setup until the new one is up an running - functioning in the same way as the current one.
Harishga 6,005 Reputation points Microsoft External Staff

2023-12-15T07:22:45.2833333+00:00

Hi@DataPeps2023
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
DataPeps2023 25 Reputation points

2023-12-15T09:52:11.7866667+00:00

Hi @Harishga

Sorry for the delay, I didn't get to look at this yesterday. I'm going to try using the package stores. Thank you for the link, it looks like it will be really helpful.

1 answer

Your answer

Smaran Thoomu 32,775 Reputation points Microsoft External Staff Moderator

2023-12-13T13:47:37.0666667+00:00

Hi @DataPeps2023

Welcome to Microsoft Q&A Platform. Thank you for posting your query.
To clone an existing Azure Data Factory (ADF) to a new ADF, you can use the Azure Portal or Azure PowerShell. However, when you clone an ADF, it doesn't include the SSIS Integration Runtime (IR) by default. You need to create a new SSIS IR in the new ADF and configure it to use the same SSISDB as the existing SSIS IR.

To create a new SSIS IR in the new ADF, follow these steps:

In the Azure Portal, navigate to the new ADF.

Click on the "Author & Monitor" button to open the ADF UI.

Click on the "Manage" tab and then click on "Integration Runtimes".

Click on the "New" button to create a new SSIS IR.

Follow the prompts to create the new SSIS IR. When prompted for the SSISDB, select "Use existing SSISDB" and enter the connection string for the existing SSISDB.

Once you have created the new SSIS IR, you can test it by creating a new pipeline that uses the SSIS IR. You can also use the "Test Connection" button in the SSIS IR settings to verify that the connection to the SSISDB is working.

Regarding the issue of not being able to create a second SSISDB on the same database, this is a limitation of SQL Server. You can only have one SSISDB per SQL Server instance. However, you can use the same SSISDB for multiple SSIS IRs in different ADFs as long as they are in the same region.

I hope this helps! Let me know if you have any further questions.
DataPeps2023 25 Reputation points

2023-12-13T15:43:54.76+00:00

Hi, thanks for taking the time to respond.

Unfortunately I don't have the option of "Use existing SSISDB" as per your suggestion in point 5. Based on your last point, I imagine it is because the current ADF is in a different region to the new one (which is part of the reason I am creating a new ADF).

I am wondering if the best option is to choose to "use package stores to manage you packages into file system...." Although I've not used this setup before and am unsure at this time how it will change how I deploy changes, or running packages. I was not looking to make any significant changes to the ADF setup until the new one is up an running - functioning in the same way as the current one.
Harishga 6,005 Reputation points Microsoft External Staff

2023-12-15T07:22:45.2833333+00:00

Hi@DataPeps2023
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
DataPeps2023 25 Reputation points

2023-12-15T09:52:11.7866667+00:00

Hi @Harishga

Sorry for the delay, I didn't get to look at this yesterday. I'm going to try using the package stores. Thank you for the link, it looks like it will be really helpful.

Answer 1

Hi@DataPeps2023
Thank you for the additional information. If you don't have the option to "Use existing SSISDB," it could be because the current ADF is in a different region than the new one, as you mentioned. In this case, using package stores to manage your packages into the file system is a good option.

When you use package stores, you can import/export/delete/run packages and monitor/stop running packages via SQL Server Management Studio (SSMS) similar to the legacy SSIS package store. You can also use dtutil command-line utility to deploy multiple packages in batches.

To learn more about managing packages with Azure-SSIS Integration Runtime package store, please refer to the following documentation
Reference:

https://learn.microsoft.com/en-us/azure/data-factory/azure-ssis-integration-runtime-package-store
Hope this helps. Do let us know if you any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Harishga 6,005 Reputation points Microsoft External Staff

2023-12-18T04:35:08.8166667+00:00

Hi@DataPeps2023
Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Share via

Cloned Data Factory with SSIS Integration Runtime

1 answer

Your answer