Truncate table clear table content

Truncate table clears the TABLE content. TRUNCATE table deletes all rows in the TABLE, but does not record the deletion of a single row. The truncate table is similar to the DELETE statement without a WHERE clause. However, the truncate table is faster and uses fewer system resources and transaction log resources. Syntax [{database_name. [schema_name]. | schema_name.}] table_name [;] parameter database_name database name. Name of the schema to which the schema_name table belongs. The name of the table to be truncated or the name of the table to delete all its rows. Compared with the DELETE statement, the truncate table has the following advantages: less transaction log space is used. The DELETE statement deletes a row at a time and records an item in the transaction log for each row to be deleted. Truncate table deletes data by releasing the data page used to store TABLE data, and only records the page release in transaction logs. The number of locks used is usually small. When the DELETE statement is executed using the row lock, the rows in the table are locked for deletion. Truncate table always locks tables and pages, rather than locking rows. Without exceptions, no pages are left in the table. After the DELETE statement is executed, the table still contains blank pages. For example, you must use at least one exclusive (LCK_M_X) Table lock to release empty tables in the heap. If the table lock is not used during the delete operation, the table (HEAP) contains many blank pages. For indexes, the delete operation leaves some blank pages, although these pages are quickly released through the background clearing process. Truncate table deletes all rows in the TABLE, but the TABLE structure, its columns, constraints, and indexes remain unchanged. To delete TABLE definitions and data, use the drop table statement. If the table contains an ID column, the counter of this column is reset to the seed value defined in this column. If no seed is defined, the default value 1 is used. To retain the ID counter, use DELETE. You cannot use truncate table for the following tables: tables referenced by the foreign key constraint. (You can intercept a table with its own foreign key .) The table that participates in the index view. Tables published by using transaction replication or merge replication. For tables with one or more features, use the DELETE statement. Truncate table cannot activate the trigger because this operation does not record the deletion of each row. Example: USE AdventureWorks; go select count (*) AS BeforeTruncateCount FROM HumanResources. JobCandidate; go truncate table HumanResources. JobCandidate; go select count (*) AS region FROM HumanResources. JobCandidate; GO