How will long running Delete Job affect an instance?

[MartinT]

Hello all,

I would like to create Delete Job (new Tokyo feature) to remove up to 2-3 million records. It's just to clean up an instance a bit. So it will run only once. It's should run on non production instance. I use condition builder to create my conditions and then click Preview. I can see few hundred thousands or more records which will be deleted.

I don't want to delete whole table and also I would like to delete related records as Delete Job will do.

I assume it will take a lot of time. The question is, if users can work normally during that time with affected tables and if it's possible to tell, how long it will take? E.g. Incident table with 700,000 records + all related stuff will be maybe up to 2,000,000 records. 

How is the Delete Job designed? Will it slowly delete all the records which matched the condition at the time of execution start and this process can take few days... or will it "hold" the table and/or whole instance so everyone is completely screwed and nobody can work on affected tables/instance?

Thanks!

[William Busby]

I used this feature to remove a table of approx 1.2 million rows. While running I found my sessions to SNOW to be slow as molasses but other users from other workstations experienced no issues. I don't recall how long it took but it was more than an hour.