Adjusting Naming Conventions, version 4.6.6.6.


Let's review what we currently have. We've built the loading process for the Company dimension table using a driver, container, automatic box, and another driver. Note the names of the integrator objects that have been built.


In the following figure, we show the loading process for the InCategory and InBrand tables. In the above case, the source driver and the container were the same. We just assembled different transformers, different automatic boxes, and wrote to different tables.


Above, you can see the processes with their respective component names. Note that the names don't follow a pattern. The tool doesn't require this pattern to be followed, but later, in processes with many components, establishing a pattern can be beneficial for organization and future maintenance of these components.


Everyone can determine their own pattern. Let's establish a rule here, which doesn't mean it's the best rule, but it's a good practice based on the experience of other projects. Let's suggest the following nomenclature:


Process, representing a standard name that identifies a component association. A subprocess, a breakdown of the identification, which may not be mandatory, plus a hyphen and then the component identifier name. The first two identifications will be standard and in uppercase.


As for the name, we'll use both uppercase and lowercase letters. Here's a suggestion for the components encompassing the loading of the Company dimension. Below is the suggested name change for the other dimensions.


Next, let's return to the integrator and implement these changes, and understand how to rename components already created in the PIS. To organize the component name change, I'll click on the Microsoft SQL Server tab, right-click, and select "Close all but this," then close this last tab. Our initial status will be the PIS with no open component tabs.


Let's start with the Driver and the Provider. The Provider, we have two Providers here, one called ProviderDW and the other ProviderDW version 2. This latter Provider was used by us only so we could understand how we create multiple Providers. I'll click on ProviderDW version 2 and delete it.


Note that we didn't establish any pattern for the Provider's name. The Provider's name is the process identifier. You can later use the Provider's name as a process to identify each component associated with that Provider.


Or not, if you're going to ensure that your entire environment will have only one Provider, you don't need to establish this name as a process. Let's move on now, click on Drivers, MS SQL Server. Here we have the Driver representing the data source.


Let's rename it, let's call it SQL Server, meaning the process will be the identifier for the source type. We'll establish as a subprocess and write "Target" and finally the name. I'll put Database Destination, and then click Update.


We now have our standard for the Driver's name. Let's now click on Data Container and let's establish here the MS SQL Server Container. We have three Containers here, and note one thing, when clicking on the Container, if I come here to Query, Table, or Command, note that the name of the Driver associated with the Container is still using the old name, of course, because the update was made at the Driver level.


To load this name here, we just need to click on Edit. We'll now see the component that is part of the Driver association within the Container and simply click Save again, without making any other modifications. Note that the names will now be loaded for the representation of the Driver within the Container.


But we also need to change the name of this Container. Let's call it Company Dimension - Company List. I'll click on Update.


Let's move on to the Embedded Lockup component. In this case, we'll call it Lockup, we won't create a Subprocess here, and then we'll put Dimension Table - Brands. Note that the reference here is still with the old nomenclature, so we'll click on Edit.


Click on Save, then Update, and let's do the same and call it Lockup - Dimension Table - Category. Again, coming from the Driver reference, click on Edit, click on Save, click on Update. Now let's click on Driver and TextFile. We have two Drivers here.


The Driver called Driver-CSVServer was just a Driver we used to show how we can save data on the server. We'll delete this Driver. Clicking now on Driver-CSVS, we'll modify this name and call it Text - Source - Brands and Categories List.


I'll click on Update. We already have the modification of the Text File type Driver. Let's now go to Data Container and select Container - Text File.


Let's click on the type and let's call it Dimension - Brands and Categories. We have to come here to Name - Path, click on Edit to load the new modified Driver name. Returning to Main, let's click on Update.


We now need to go to the transformations. So let's click here on Data Container - Transformations. We have four transformations here.


Let's start with the Loaded-in-Brand that we're going to modify and use as a standard. Dimension, Transformation and then we'll put Transformation - Brands. Of course, coming in Source, click on Edit, Save to load the new name, and let's click Update.


Let's repeat for the second one where we're going to type Dimension - Transformation - Transformation - Category. And again in Source, click on Edit, click on Save, Update. Let's now move to the Lockup transformation.


Let's remember that for a table to participate in the lockup process, it needs to be within the transformation, even if there is no component to modify its original layout. So, first, I'll click on Edit and search, clicking on Save, the new name. And here we'll put Lockup - Transformation - Dimension Table - Brands.


Let's put Table - Dimension - Brands. And for the category, we'll put the same name that we put in Brands. The same name formation. Lockup - Transformation - Table - Dimension - Category. In Source, click on Edit, click on Save, click on Update. Finally, let's go to the Automatic Boxes.


First, let's put here, Dimension - Transfer and Load - Brands. Here in Source, we have to click on Edit and then on Save. And in Target, click on Edit and then on Save.


Click Update. Let's go to the second one. Dimension - Transfer - Load - Company.


In Source, click on Edit, click on Save. In Target, click on Edit, click on Save. Update.


Finally, the last one. Dimension - Transfer - Load - Dimension - Category. Click on Source, click on Edit, click on Save.


Click on Target, click on Edit, click on Save. Update. We now have all the component names using a pattern.


And from now on, we will always use this pattern. Thank you, and until the next video.