Microsoft SQL Server Database Quiz Questions

The TRUNCATE TABLE command is minimally logged and cannot be rolled back if executed outside a transaction.

TRUNCATE TABLE cannot be used if there are foreign key constraints unless those constraints are removed or handled.

TRUNCATE TABLE resets the identity column value to its seed value, unlike DELETE.

TRUNCATE TABLE removes all rows from the table and does not support WHERE clauses to filter rows.

TRUNCATE TABLE generates minimal logging compared to DELETE operations, which log each row deletion.

TRUNCATE TABLE is minimally logged, but it can be rolled back if used within a transaction.

TRUNCATE TABLE only removes rows and does not affect the table structure or column definitions.

TRUNCATE TABLE does not affect indexes beyond removing all rows from the table, so the indexes are still there but may be fragmented.

TRUNCATE TABLE is not allowed on tables that are part of a replication topology in SQL Server.

TRUNCATE TABLE can be used on partitioned tables, affecting all partitions by removing all rows.

TRUNCATE TABLE is typically faster than DELETE for removing all rows because it is minimally logged and does not generate row-by-row log entries.

TRUNCATE TABLE does not activate DELETE triggers, as it is not logged like DELETE statements.

TRUNCATE TABLE operations are minimally logged but can be rolled back within a transaction, restoring the table to its previous state.

TRUNCATE TABLE is suitable for quickly removing all rows from a large table without affecting the table schema.

TRUNCATE TABLE can be used even if there are triggers on the table; however, triggers will not be executed as TRUNCATE does not generate row-level operations.

TRUNCATE TABLE is faster and uses less log space compared to DELETE because it is minimally logged.

TRUNCATE TABLE removes all rows from a table while preserving the table structure, unlike DROP TABLE which removes both data and table structure.

TRUNCATE TABLE is restricted on tables with foreign key constraints unless those constraints are removed or modified.

TRUNCATE TABLE does not affect the table structure; it only removes all rows from the table.

TRUNCATE TABLE keeps the table structure and constraints intact while removing all rows.

TRUNCATE TABLE does not fire DELETE triggers because it does not operate row by row.

TRUNCATE TABLE is restricted on tables involved in replication.

TRUNCATE TABLE can be efficiently used to clear data from a large partitioned table as it operates on all partitions at once.

TRUNCATE TABLE resets identity column values to their seed values, unlike DELETE.

TRUNCATE TABLE generates minimal logging compared to DELETE, which logs each row deletion.

TRUNCATE TABLE is recommended for clearing all rows efficiently while maintaining the table schema.

TRUNCATE TABLE can clear all rows from a table, including those in partitioned structures, in one operation.

TRUNCATE TABLE is suitable for quickly deleting all rows while keeping the table structure and constraints intact.

TRUNCATE TABLE does not affect the table’s structure or schema, it only removes rows.

TRUNCATE TABLE does not activate DELETE triggers, unlike DELETE which triggers associated operations.

TRUNCATE TABLE resets the identity column values to the seed value, which is not the case with DELETE.

TRUNCATE TABLE will remove all rows and reset identity columns to their initial seed values.

TRUNCATE TABLE is suitable for clearing data from large tables while preserving the table schema.

TRUNCATE TABLE offers better performance compared to DELETE because it is minimally logged and faster for removing all rows.

TRUNCATE TABLE removes only rows but preserves constraints and indexes, unlike DROP TABLE which removes the table structure.

TRUNCATE TABLE is appropriate for clearing all data while preserving the table structure.

TRUNCATE TABLE is suitable for quickly removing a large volume of data while not affecting indexes or table structure.

TRUNCATE TABLE maintains the table’s constraints and structure after removing all rows.

TRUNCATE TABLE is suitable for quickly removing all rows without activating DELETE triggers.

TRUNCATE TABLE is appropriate for removing all data and resetting identity column values.

TRUNCATE TABLE is minimally logged and does not fire DELETE triggers. It also resets identity columns.

TRUNCATE TABLE is suitable for removing all rows quickly without affecting the table schema or constraints.

TRUNCATE TABLE cannot be used on tables with foreign key constraints or those participating in replication.

DELETE and TRUNCATE TABLE both remove rows, but TRUNCATE TABLE is faster and resets identity columns. DROP TABLE removes the table structure.

TRUNCATE TABLE is faster and uses less log space compared to DELETE, but DELETE can delete specific rows based on conditions.