Edit Question - KnowledgeHub

Title Body

I am trying to use Dapper support my data access for my server app. My server app has another application that drops records into my database at a rate of 400 per minute. My app pulls them out in batches, processes them, and then deletes them from the database. Since data continues to flow into the database while I am processing, I don't have a good way to say delete from myTable where allProcessed = true . However, I do know the PK value of the rows to delete. So I want to do a delete from myTable where Id in @listToDelete Problem is that if my server goes down for even 6 mintues, then I have over 2100 rows to delete. Since Dapper takes my @listToDelete and turns each one into a parameter, my call to delete fails. (Causing my data purging to get even further behind.) What is the best way to deal with this in Dapper? NOTES: I have looked at Tabled Valued Parameters but from what I can see, they are not very performant . This piece of my architecture is the bottle neck of my system and I need to be very very fast.

Tags (comma-separated) Cancel