How would you design a customer table with CustomerID as the primary key and columns for customer name, phone, email, address, and last updated date?

When designing a customer table, you start by defining the primary key, which in this case is CustomerID. It should be a unique, non‑nullable column, often an auto‑increment integer or a UUID. Next, decide on data types: CustomerName as VARCHAR(255), PhoneNumber as VARCHAR(20) to accommodate formatting, Email as VARCHAR(255) with a UNIQUE constraint, Address as a composite column or separate columns (Street, City, State, Zip) depending on normalization needs. The LastUpdatedDate column should be a TIMESTAMP with a default of CURRENT_TIMESTAMP and an ON UPDATE clause to automatically capture changes. Add NOT NULL constraints where appropriate, and consider indexing frequently queried columns like Email or PhoneNumber. If you anticipate high write volume, partition the table by a business key such as Region. Finally, document the schema and enforce referential integrity if the customer table is referenced by orders or transactions.