About this module
This module shows you how to manage data updates in a .csv file stored on Dropbox and synchronise the changes to a SQL Server database, using Universal Platform constraints.
Module 1 of this tutorial explained how to configure the methods used to extract data in a .csv file from Dropbox to a SQL database, and successfully import the required data.
So what does this module cover? Well, the scenario is this:
Module 2 of this tutorial explains how to configure the constraints used when extracting data in a .csv file from Dropbox to a SQL database, to ensure only new records and updated data is imported. So in this module:
- You will start by querying the database table you created in Module 1 to view the data in the database.
- You will then run the pipeline to import data from the HR.csv file to your database table.
- At this stage you will see that the records are duplicated in your database table. This is because there are no constraints in place and so data is re-imported as new instances.
- Once you have analysed the imported data, you will clean up your database table and configure a constraint to restrict the data imported, based on specific entity attributes in your data model.
- You will run the pipeline again and analyse the data imported to your database table with the constraint applied.
- There should now be no duplicate records when you re-import HR.csv to you database table.
- You will then make changes to information in HR.csv and import the updated data to your database.
- You will complete the module by querying the database table to ensure the data is in the table.
Now that you are familiar with what we are going to do in this module, let's begin!