Guaranteeing uniqueness for an entity can be a challenge. If each

entity is not assigned a unique identifier, its attributes may not guarantee uniqueness. This leads to problems with updates and retrieval of data. In the online clothing store scenario presented in the Introduction to this unit, imagine the problems that can occur if customers are not uniquely defined within the database. For example, if there are five customers named Bill Smith, each time one of them places an order, there is a potential for all five Bill Smiths to receive and be billed for the order. choose any organization—a bank, a hospital, a store, or a coffee bar, for example—and describe how to uniquely define the customer. Assume that this is a relational model and that you are not creating a single numeric or alphanumeric unique identifier for the customer, such as a customer number.
With these thoughts in mind, analyze ways to ensure uniqueness and the existence of data. Consider the attributes you will store, and discuss each of the following:
What happens if one of the fields is unknown?
Are all the required fields always recorded for a customer?
How can you prevent duplicate records?
Are “William Jones,” “Bill Jones,” and “W. J. Jones” the same customer? If they are, how could you connect them?
Do any of the defined attributes have more than one value?
How can you ensure that all types of customers fit your definition?
Discuss whether there really is a unique definition for a customer and whether your definition works equally well for all businesses.
*****I need it today so badly, please help*****