February 13, 2012 at 11:23 am
Hi,
I got a delete statement which performs cascade delete to some 20 sub tables.
I got necessary indexes on all the tables.
Problem is i got around 300K records in my parent table, so when that delete statement starts running it goes fine with avergade duration of 0ms with index seek on all the tables. After reach to 20k or more the average duration is going up to 450 ms and some of the child tables are having index scans which used to have index seek before and it is slowing down the load process completely.
Can some one suggest me any thing that i can do to fatsen that delete. I used forceseek option too but it is getting applied to just the parent table(which is supposed to be).
Thank you
February 13, 2012 at 11:57 am
Please don't cross post. Direct all replies here. http://www.sqlservercentral.com/Forums/Topic1251377-392-1.aspx
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply