• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 642
  • Last Modified:

Truncate 300GB table size

How should I plan to truncate our table with 300GB of data, this table unfortunately have heavy insert  24X7X365 days, what will happen during the truncate with insert statement ?
0
motioneye
Asked:
motioneye
  • 3
  • 2
  • 2
  • +5
8 Solutions
 
JoeNuvoCommented:
base on documents,
said truncate large table still fast.
since the Physical "delete" will perform in background

http://msdn.microsoft.com/en-us/library/ms177570(v=SQL.90).aspx
http://msdn.microsoft.com/en-us/library/ms177495(v=SQL.90).aspx
0
 
Rajkumar GsSoftware EngineerCommented:
The query
"TRUNCATE TABLE YourTableName"
would delete all records
+
resets IDENTITY column

Raj
0
 
mayank_joshiCommented:
i would like to add one point that TRUNCATE is not allowed for a table referenced by a Foreign Key constraint.
0
Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

 
Aaron ShiloChief Database ArchitectCommented:
hi

truncate command is a fast executing command becouse you only udate the the system tables that the table you truncated is empty and all extent information regarding that table is delete from system tables. (this is why the command is fast no actual action is performd on the table it self).

you will bearly feel a small lag in inserts till the system tables are udates .

0
 
sventhanCommented:
<< what will happen during the truncate with insert statement

If you running truncate on a LIVE DB, isn't that you going to loose few data? Is that OK to loose the DATA? I'm talking about the insert happening while you running the truncate.
0
 
sventhanCommented:
OK. I see the lock going on and you're safe I guess.
0
 
QlemoDeveloperCommented:
To summarize:
* you need to make sure you have no foreign key references on the table
* the truncate itself is executed very fast, among others because no logging takes place
So you just need to try. You can do that anytime, but of course you are loosing all data stored in that table.

If you have foreign keys, you only can perform a very costly delete operation, splitted in slices of e.g. thousands of records; or rename the table, and immediately create a new empty copy of it to be filled again.
0
 
Anthony PerkinsCommented:
>>executed very fast, among others because no logging takes place<<
If you are referring to the Transaction Log, you may want to double check that.
0
 
QlemoDeveloperCommented:
"No logging" = "almost no logging", then. The removed pages are not logged, as they would with DELETE.
0
 
KetGuruCommented:

Truncate table will not lock a table and you are mentioning that this table is in use all the time, you want to truncate it. so assumption that this table is log table and have no constraint/dependency with other tables. Should not be an issue. size does not make difference with truncate command.
0
 
sventhanCommented:
< Truncate table will not lock a table

http://msdn.microsoft.com/en-us/library/ms177570.aspx

From the link

ewer locks are typically used.

When the DELETE statement is executed using a row lock, each row in the table is locked for deletion. TRUNCATE TABLE always locks the table and page but not each row.

@ KetGuru

>>> Is MSDN wrong?
0
 
Anthony PerkinsCommented:
>>"No logging" = "almost no logging", then. The removed pages are not logged, as they would with DELETE.
...
Truncate table will not lock a table <<

How about we state all the facts correctly as stated in SQL Server BOL:

Less transaction log space is used.
The DELETE statement removes rows one at a time and records an entry in the transaction log for each deleted row. TRUNCATE TABLE removes the data by deallocating the data pages used to store the table data and records only the page deallocations in the transaction log.

Fewer locks are typically used.
When the DELETE statement is executed using a row lock, each row in the table is locked for deletion. TRUNCATE TABLE always locks the table and page but not each row.

Without exception, zero pages are left in the table.
After a DELETE statement is executed, the table can still contain empty pages. For example, empty pages in a heap cannot be deallocated without at least an exclusive (LCK_M_X) table lock. If the delete operation does not use a table lock, the table (heap) will contain many empty pages. For indexes, the delete operation can leave empty pages behind, although these pages will be deallocated quickly by a background cleanup process.

...

Microsoft SQL Server 2005 introduces the ability to drop or truncate tables that have more than 128 extents without holding simultaneous locks on all the extents required for the drop.
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 3
  • 2
  • 2
  • +5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now