 Hello, welcome to SSUnitech. So, see this side and this is continuation of SSIS tutorial. So, today we gonna discuss about logins part 2. So, in our last video we have discussed basics about logins and we have discussed 2 log providers. So, if you haven't watched last video of this video series. So, I would strongly recommend to watch that video before going forward. So, let's start with SSIS log provider for SQL profiler. The SQL server profiler log provider which writes traces that you can view using SQL server profiler. The default filename extension of this provider would be .trc. So, go to on ssdt and this is our example as we have discussed in our last video. So, I am going to use that one. Go to on logging. Here, I would like to add one more. This is for SQL server profiler. And here I need to configure. Then I need to add a file. So, we can click on new. Then create file. We can browse. And here I would like to use SQL profiler.trc. I can click on open. Then okay. Go to on details. So, I would like to use on error and go to on advance. It will capture the machine name, operator name, source name, text message and data bytes. Now click on okay. Now save this package and execute. So, once our package will be executed, package will be failed because in our execute SQL task we have specified one divided by zero. That is not possible. So, cancel this and go to on folder. And this is our trace file. So, I would like to open this and it will be opened in SQL server profiler. So, this is our SQL server profiler. And here, as we can see, this is our event class. So, this is our operator name. And this is our source name. That is fine. And this is our text data. So, in our text data, as we can see, executing the query, select one divided by zero, filled with the following error divided by zero error in countered. So, this is our error. So, we can cancel. So, this is for SQL server profiler. Next lock provider would be windows event log. So, go to on ssgt and here go to on logging. And I would like to use windows event log. Now we can click on add and we can select. So, here in configuration, we are not having anything. Go to on details. So, we want to capture all the information which we have captured in our last lock provider. So, I can click on okay. Now we can save this and execute our package. So, package should be filled. That is fine. Stop this package. Now we need to check the windows event log. So, here we need to go to on event viewer. So, inside this event viewer, go to on windows log then application. It would take few seconds. So, here as we can see error. So, in this error, select one divided by zero, filled with the following error divided by zero error in countered. So, this is our error, which has been captured in windows log event. And our next and last provider would be xml file. So, ssis log provider for the xml file. So, it will write log entries to the xml files. The default file name extension of this provider would be dot xml. So, go to on ssgt then go to on login. In this login, I would like to add for xml files as well. So, this is for xml. So, here again we need to go to on configuration then create a new connection and we want to generate a file create file then we can browse. And here I want to capture log data dot xml. Now we can click on open. That is fine. Go to on detail. So, we want to capture all the informations which we have captured in our last block provider. So, click on OK. Now we can save it and click on start. So, packets should be filled. That is fine. Stop this packets and go to on folder. So, here as we can see this is our xml. So, we can open in notepad. So, it has xml data and we can see over here and we will try to read the error message. So, this is our error message. Select 1 divided by 0 filled with the following error divided by 0 error encountered. So, that is fine. So, these are the log providers or label in SSIS where we can store our log message. So, here we cannot use SQL Server profile log provider in packets that is running in 64-bit mode. So, we need to remember this. Next, as we have seen the SQL Server log provider uses the OLADB connection manager. Others like text file, SQL Server profiler, XML file log providers uses file connection managers. The windows event log provider doesn't use any connection manager because it writes directly to the windows event log. So, I hope you have understand how we can use logging in our SSIS package and how we can store the logs in our different different formats which is our label in SSIS. As we have discussed, there is five formats. So, thank you so much for watching this video. If you 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. Thank you so much.