SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Proper Indexing For Trigger Initiated Inserted Scan


Proper Indexing For Trigger Initiated Inserted Scan

Author
Message
cr259
cr259
Grasshopper
Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)

Group: General Forum Members
Points: 19 Visits: 131
Is there a best practice for creating index to reduce the IO for inserted scans that originate from a trigger? I have a table with roughly 2 million rows that has an insert and an update trigger that fires every time a new row is inserted or when an existing row is updated. From the estimated execution plan, the EstimatedIO for these scans is ~64. Currently, the table only has a clustered primary key index. Is there a specific way to approach index for inserted scans to reduce the overall IO of the process?

**edit**
My only thought right now is to read the inserted row into a temp table, and then create a clustered index on the primary key of the temp table. The thinking is that the trigger is making subsequent calls for the inserted row, which causes a table scan to retrieve the data. Anything behind this logic?
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search