July 19, 2018 at 1:02 pm
Hi all,
First off, I have a database that has over 250 million records and am in the process of clearing out the old records (the application fine tuning wasn't cleaning out the old records during the scheduled job), my question is why (or how) records are still being ingested when a delete statement is running? I am using a WHERE statement and there are no connections being made to the database except for mine.
Thanks!
July 19, 2018 at 2:04 pm
Kenn Edwards - Thursday, July 19, 2018 1:02 PMHi all,First off, I have a database that has over 250 million records and am in the process of clearing out the old records (the application fine tuning wasn't cleaning out the old records during the scheduled job), my question is why (or how) records are still being ingested when a delete statement is running? I am using a WHERE statement and there are no connections being made to the database except for mine.
Thanks!
Well, hard to say since we can't see what you see. Could be quick connecting processes, triggers, scheduled jobs. Just not sure.
Data doesn't just appear out of thin air.
July 19, 2018 at 2:10 pm
are you using nolock hint, read uncommitted isolation?
***The first step is always the hardest *******
July 19, 2018 at 9:02 pm
Kenn Edwards - Thursday, July 19, 2018 1:02 PMHi all,First off, I have a database that has over 250 million records and am in the process of clearing out the old records (the application fine tuning wasn't cleaning out the old records during the scheduled job), my question is why (or how) records are still being ingested when a delete statement is running? I am using a WHERE statement and there are no connections being made to the database except for mine.
Thanks!
Can you clarify what you mean by "Records are still being ingested", please?
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply