Expand my Community achievements bar.

Adobe Campaign User Groups are live now. Join our Adobe Campaign User Groups and connect with your local leaders!
SOLVED

Blank data is getting inserted for primary key column in data schema

Avatar

Level 3

Hi Team,
For custom data schema we have created email as our primary key.

While inserting the data with data loading activity we noticed that there are certain records with blank email address still they got inserted into the database schema.
May I know how come a column with primary key is taking empty values in data schema

Following is the screenshot of email as primary key 

mustufam5967803_0-1681193336720.png


Blank data insertion screenshot 

mustufam5967803_2-1681193665880.png

 

 

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

@mustufam5967803 ,

There could be several reasons why this may occur:

  1. Schema Design: The schema design may allow for empty or null values in the primary key column. For example, the primary key column may not have been defined with a NOT NULL constraint, or it may have been designed to allow null values.
  2. Database Management System (DBMS) Settings: The settings of the specific DBMS being used may allow for empty or null values in the primary key column. For example, some DBMS allow for null values in primary key columns by default, or there may be a specific configuration or setting that allows for this behavior.
  3. Data Loading Process: The data loading process used to insert data into the table may not be enforcing the primary key constraint properly. For example, the data loading process may not be validating or checking for empty or null values in the primary key column before inserting the data into the table.

It is important to review the schema design, DBMS settings, and the data loading process to determine why empty values are being allowed in the primary key column.

View solution in original post

1 Reply

Avatar

Correct answer by
Employee Advisor

@mustufam5967803 ,

There could be several reasons why this may occur:

  1. Schema Design: The schema design may allow for empty or null values in the primary key column. For example, the primary key column may not have been defined with a NOT NULL constraint, or it may have been designed to allow null values.
  2. Database Management System (DBMS) Settings: The settings of the specific DBMS being used may allow for empty or null values in the primary key column. For example, some DBMS allow for null values in primary key columns by default, or there may be a specific configuration or setting that allows for this behavior.
  3. Data Loading Process: The data loading process used to insert data into the table may not be enforcing the primary key constraint properly. For example, the data loading process may not be validating or checking for empty or null values in the primary key column before inserting the data into the table.

It is important to review the schema design, DBMS settings, and the data loading process to determine why empty values are being allowed in the primary key column.