DELETE

INSERT, UPDATE

SELECT

CREATE

To perform data analysis and reporting.

To optimize database queries.

To handle user authentication.

The purpose of DDL in database management is to define and manage the structure of the database.

A primary key is a unique identifier for a record in a database schema.

A primary key is an optional field in a database schema.

A primary key can have duplicate values in a database schema.

A primary key is a type of foreign key in a database schema.

A view can store data physically, while a table cannot.

A table can only be created from a view, not the other way around.

A table is a temporary storage, while a view is a permanent storage.

A table stores data physically, while a view is a virtual representation of data based on a query.

DELETE FROM table_name WHERE condition;

INSERT INTO table_name (column1, column2);

UPDATE table_name SET column1 = value;

CREATE TABLE table_name (column1 datatype, column2 datatype, ...);

Foreign keys link tables and enforce referential integrity in relational databases.

Foreign keys are used to create indexes on tables.

Foreign keys store data in a single table only.

Foreign keys are primarily for data encryption.

Ignore data types and constraints altogether.

Use only primary keys for data integrity.

Use primary keys, foreign keys, constraints, and triggers.

Rely solely on application-level validation.

The purpose of creating indices in a database is to enhance query performance by speeding up data retrieval.

To create backups of the database data.

To reduce the size of the database files.

To enforce data integrity and constraints.

Exporting the ER diagram is not possible from any database management tool.

You can only export the ER diagram as a PDF file.

The process involves using a database management tool to export the ER diagram in a chosen format.

The process requires manual drawing of the ER diagram on paper.

DROP TABLE

REMOVE TABLE

DELETE TABLE

CLEAR TABLE

Use 'CREATE TABLE' to import data

Use 'SELECT INTO' for data import

Use 'INSERT INTO' for all databases

Use 'LOAD DATA INFILE' for MySQL, 'COPY' for PostgreSQL, or 'BULK INSERT' for SQL Server.

Constraints are crucial for maintaining data integrity and enforcing business rules in a database.

Constraints are only used for indexing data in a database.

Constraints are optional and can be ignored during schema design.

Constraints have no impact on data retrieval performance.

Adding a new 'Orders' table without any relationships to existing tables.

Changing the 'Users' table to remove the 'email' column.

Modifying the 'Products' table to add new columns for 'color' and 'size'.

Renaming the 'Categories' table to 'Items' without altering its structure.

Verify relationships by checking entities, cardinality, foreign keys, meaningfulness, and consistency.

Check only the primary keys of entities.

Assume all relationships are correct without verification.

Ignore cardinality and focus on attributes only.