Post reply

Clustered Index Delete

  • March 28, 2014 at 10:39 am

    #396496

    Hi,

    I want to know more details about the Clustered Index Delete. Is that Clustered Index Delete in the execution plan is good or bad or we can neglect that cost. Is there any way to avoid that clustered Index delete operator from the execution plan.

    Thanks,

    Ramana

  • March 28, 2014 at 11:29 am

    #1701248

    Not likely. If you are deleting data, the clustered index needs to reflect that.

  • March 28, 2014 at 12:23 pm

    #1701276

    A clustered index stores the data. So when you run a delete statement, it goes to the clustered index to delete the data. That's how it works.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • March 28, 2014 at 12:56 pm

    #1701293

    Hi,

    What I understand is

    So clustered Index delete or insert means there is no sign for bad performance. Just it is showing that delete or insert operation occurred.

    Please correct me if I understand wrong.

    Thanks,

    Ramana

  • March 28, 2014 at 1:26 pm

    #1701299

    Nope. You got it. If you're inserting to a table with a clustered index, it's inserting into the clustered index. That event, by itself, is absolutely not a performance problem.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply