Skip to main content

SQL Server: What is the difference between DELETE and TRUNCATE command?

Following are the differences between DELETE and TRUNCATE:

TRUNCATE
DELETE
TRUNCATE is DDL Statement
DELETE is a DML command
TRUNCATE cannot have WHERE Conditions
DELETE can have WHERE conditions
TRUNCATE does not fire trigger
DELETE Fires TRIGGER
TRUNCATE reset the identity to 0 (if table have any)
DELETE does not RESET Identity
TRUNCATE Release the table’s spaces to System
DELETE removes the records but will not release the space to the system
TRUNCATE cannot be used against the table that is referenced by a FOREIGN KEY constraint.
DELETE can be used in tables reference by a Foreign Key and tables involved in Indexed view
TRUNCATE cannot be used against the table used in Indexed view
DELETE can be used against the table used in Indexed view
TRUNCATE apply Fewer table locks
DELETE apply more locks to the table
TRUNCATE cannot be used against the tables involved in TRUNCATE transactional replication or merge replication.
DELETE can be used against table used transactional replication or merge replication
Less Transaction Log entry because TRUNCATE TABLE removes the data by de-allocating the data pages used to store the table data and records only the page de-allocations in the transaction log and hence TRUNCATE is fast
DELETE FROM TABLE command logs each record in transaction log, hence DELETE is slow.

Note: TRUNCATE can be roll backed. Many programmers think that TRUNCATE can’t be roll backed.
Labels:

Comments

Post a Comment

Popular posts from this blog

Error 405 : ASP.NET Core Web API PUT and DELETE Methods not allowed

Recently, while working with .Net core API I came across the issue of “Error 405 — Methods not Allowed” After some research, I found out that both GET and POST requests working fine but neither PUT nor DELETE requests working. Another thing is that the PUT and DELETE request was also working fine on my local machine but failed when we host on our Azure server. When I explored the issue on the web it led me to the conclusion that WebDAVModule seems to set PUT and DELETE request methods disabled by default and due to that PUT and DELETE throw 405 errors. To make the PUT and DELETE requests work, we need to override the WebDAVModule setting in web.config file by adding the below settings under “ system.webServer ”. < system.webServer >   < modules runAllManagedModulesForAllRequests = " false " >     < remove name = " WebDAVModule " />   </ modules > </ system.webServer > There may be 2 web.config files in y...
Post a Comment
Read more

C#: Merging Excel cells with NPOI HSSFWorkbook

In this post we’ll see how to merge the two or more cell with each other while creating the excel sheet using NPOI . Mentioned below is code to merge multiple cells, in this example we are merging first cell to fifth cell of first row (you can adjust row or cell range by passing particular parameters in CellRangeAddress). //Created new Workbook var hwb = new NPOI.HSSF.UserModel. HSSFWorkbook (); //Create worksheet with name. var sheet = hwb.CreateSheet( "new sheet" ); //Create row and cell. var row = sheet.CreateRow(0); var cell = row.CreateCell(0); ; //Set text inside cell cell.SetCellValue( "This is Merged cell" ); cell.CellStyle.WrapText = true ; //define cell range address // parameters: -> first row to last and first cell to last cell var cra = new NPOI.SS.Util. CellRangeAddress (0, 0, 0, 4); //Add merged region to sheet. sheet.AddMergedRegion(cra); Hope this solution helps you J
4 comments
Read more

How to set Swagger as the default start page for API hosted on the Azure web app?

I created an Asp.Net Core 2.x Web API and configured Swagger on it, below is the code added in Configure method under Startup.cs file, for full swagger configuration, check here //Add swagger configuration app.UseSwagger(); app.UseSwaggerUI(c => {     c.SwaggerEndpoint( "../swagger/v1/swagger.json" , "Test API V1" ); }); On my local machine when I run the API it is automatically redirected to the Swagger page. However, when I hosted this API as an Azure web app it is not redirecting directly to the Swagger and to access the swagger, I had to append /swagger in the URL, for example, https://testapi.azurewebsites.net/swagger/ Solution: Set RoutePrefix to string.Empty under app.UseSwaggerUI like below: app.UseSwaggerUI(c => {     c.SwaggerEndpoint( "../swagger/v1/swagger.json" , "Test API V1" );      c.RoutePrefix = string .Empty; // Set Swagger UI at apps root }); And that’s it, now when you b...
Post a Comment
Read more