UUID creation - don't repeat it at the moment of the insertion of new data

[marod1971]

I want to implement to create UUID using Alteryx, but my concern is at the moment to insert new data to the Teradata table. This table is a historical table, and UUID is the unique primary key. I want to know if there is a way to make sure that the UUID doesn't create a key that is already in the table. Thanks in advance.

[aatalai]

@marod1971 is the UUID comprised of only digits? or either just letters or a combination of letters and digits?

[marod1971]

It's a combination of letters and numbers

[danilang]

Hi @marod1971 

The probability of a UUID collision is exceedingly small, but not zero.  The only way to be sure is to have some collision catching method.  Either read all the UUIDs from the database and compare or insert the data into a temporary table and have a trigger that looks for collisions on insert and generates a new one if required.

Dan