 Hey guys, welcome to SSUNitech facility side and today we are going to discuss about the integration runtime. So integration runtime is very important concept inside the SEO data factory and we can also say that the integration runtime is the backbone of SEO data factory. So what is integration runtime and where we can use that? So go to the next slide and we will try to understand. So what is integration runtime? So the integration runtime is the compute infrastructure used by SEO data factory to provide the following data integration capabilities across different network environments. So basically inside the ADF we are going to load the data from any one location to another location as a ideal tool. So it is going to provide a compute infrastructure and this compute infrastructure will provide the facility to move the data between different network and environments. So the first option that we can see data flow. So basically data flow it executes the data flows in managed SEO compute environment. So for the data flow we did not discuss till now but in our upcoming videos we will be going to see in the detail next in the data movement. So we have seen about the copy data activity. So it is going to copy the data from one source to another source and here by using the integration runtime it will provide the facility to move the data from public or the private network. So public network is the SEO network where we can directly connect with the SEOs and the private network that could be your SQL server that is locally installed on your machine that is your on-prem environment. So that is the private network. Next is the activity dispatch. So dispatch and monitoring transformation activities running on the variety of compute services such as SEO Databricks, SEO HD Insights, ML Studio as well and we are also SEO SQL Database and SQL Server and many more. So these are the activity dispatch services. Next is the SSI's practice execution. If you have created your SSI's package and without making the changes on your package we only want to execute the package by using the SEO Data Factory. So we can have the option inside the integration runtime. So we can set the integration runtime for that and we can execute that. Next is integration runtime types. So Data Factory offers three types of integration runtime that you can see the SEO one, self-hosted IR and last is SEO SSI's IR. So these type of IRs are available that is integration runtime and we can choose according to our requirement. So the best as per our requirement we can choose between. So the first one that we can see the SEO one. So SEO can be accessed inside the data flow, inside the data movement, inside the activity dispatch and that we can also access inside the private network. Next is the self-hosted IR. So self-hosted IR can be used for the data movement and activity dispatch. So it cannot be used by data flows inside the SEO Data Factory. So that we can see inside the self-hosted IR. So this can be used inside the private network as well for the data movement and activity dispatch. And the last one that is the SEO SSI's. So the SEO SSI's can be used for executing the SSI's packages. So that can be accessed inside the public and private network both. So mainly we are having these three types of the integration runtime. So go to the browser and we'll try to see in the practical. So if you are following my videos so we have created a pipeline for the copy data. So inside the copy data as we can see we are going to load the data from your SQL from one table to another table. So here we have created one employee under the source data set. So if we go and we'll try to see under this data set. So we are using this SQL SSU link service. So this link service will use the integration runtime to connect with your source. So here we can see first we are having the integration runtime. Second we have the link service and third we have the data set. If we want to create the data set so data set will use the link service and link service will use the integration runtime. So if we can edit from here then we can see if we can scroll a little bit downside then here we can see connect via integration runtime that you can see here. So if we can click on this so it is going to provide the integration runtime is the compute infrastructure used by data factories to provide data integration capabilities across different network environments. And as your integration runtime can be used to connect data stores and compute services in the public network. So public network with your Azure network. And here we can see with the public accessible endpoints. And here we can see the use SL fostered IR for private and on-prem networks. So that is the definition for the integration runtime is you can also check from here. So here we can see auto resolve integration runtime by using this integration runtime we are created this link service. So let me cancel this and go to the manage side and under the manage here we can see the integration runtime. So let me go there. So by default we will be having this integration runtime. So while you are going to create the Azure data factory this IR will be available there. So this IR will be working behind the scene under the link service to connect with your source or destination. See here it is like monitor option. And second here we can see for the code for this IR. And we don't have the option to delete this IR. So this IR is system generated and we cannot modify or delete. If you want to create the new IR then we can click on the new and it will open this window. And here we have the option to create the Azure self hosted IR and Azure SSIS. So these two types of IR can be created. So that we will see in our upcoming videos. Don't worry for now. Go to the next and here as we can see we are having this data factory. So this data factory is using for the Azure type of IR that is by default any system generated. So while we are using this type of IR. So it will be going to consume under the storage accounts. So if your source or destination is storage account then this type of IR can be used. Similarly for the Azure SQL DB. So we have created the copy data activity. And where we have used the Azure SQL DB as a source and destination. So it has used Azure IR and last for the Azure snaps. So if your source or destination is in Azure snaps then we can also use that. Similarly for the second option that is again for the Azure IR. So in this option we can see the same thing. If you can go and check for the third one. So this is for the self hosted IR. So under the self hosted IR it is going to connect with the SQL server. So SQL server is your on-prem environment. So if you want to connect with your on-prem SQL server then we have to use the self hosted IR that you can see here. And last one that is the Azure SSIS integration runtime that you can see here. So while we are going to execute the SSIS packages then we are required to have the Azure SSIS integration runtime under the data factory. And that will be going to execute under the Azure SQL DB. So we will see in detail about this. So don't worry for now. Here you can only understand we are having three types of IR and where we can use all those. So that we have seen. So thank you so much for watching this video. If you really like this video please subscribe our channel to get many more videos. Don't forget to press the bell icon to get the notification of our newly uploaded videos. See you in the next video.