Final Answer:
Certainly! Here are the SQL statements to create the tables with appropriate constraints:
```sql
CREATE TABLE Branch (
branchName VAR CH AR(15),
street VA RC HAR(30),
city VAR CH AR(20),
PRIMARY KEY (branchName)
);
CREATE TABLE Account (
accountNum INTEGER,
branchName VA RCH AR(15),
balance INTEGER,
PRIMARY KEY (accountNum),
FOREIGN KEY (branchName) REFERENCES Branch(branchName) ON DELETE CASCADE
);
CREATE TABLE Customer (
customerSSN INTEGER,
street VARC HAR(30),
city VARCH AR(20),
PRIMARY KEY (customerSSN)
);
CREATE TABLE Deposit (
customerSSN INTEGER,
accountNum INTEGER,
amount INTEGER,
FOREIGN KEY (customerSSN) REFERENCES Customer(customerSSN) ON DELETE CASCADE,
FOREIGN KEY (accountNum) REFERENCES Account(accountNum) ON DELETE CASCADE
);
```
Step-by-step explanation:
These statements create tables for Branch, Account, Customer, and Deposit. They establish primary keys for each table and enforce referential integrity using foreign keys with "on delete cascade" to ensure that related records are deleted when referenced records are deleted, maintaining referential integrity.
These SQL statements create tables for Branch, Account, Customer, and Deposit. Each table has its primary key defined, ensuring uniqueness. The "Branch" table holds branch information, while "Account" links to branches and stores account details. "Customer" retains customer data, and "Deposit" records deposits, connecting customers to their accounts.
The foreign key constraints maintain referential integrity, permitting cascading deletions for associated records in the event of primary key deletions, safeguarding relational coherence within the database.