Best practice: deleting 30 Million annotation records

(0) Share

Report

Posted on by Manish

482

We are planing to delete 30 Million annotation records from our production DB. For that we wrote the SP to update the deletionstatuscode=2 and and hand over to crm system to delete it from there end.

Is this this the right way to delete the records from CRM?

How log will it take to perform this update task?

while doing async delete by crm service what time and cpu resources will get consumed?

will CRM async service will take care for use of CPU resource?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Royal King 27,686 on at

Like (0)

Report

I would create multiple bulk delete job with created on date of record to group deletion based on like created on year to delete these many records and let system take care of all the resource handling.

Was this reply helpful? Yes No
Suggested answer

Bruno Lucas 5,421 on at

Like (0)

Report

Bulkdelete is the best approach.

msdn.microsoft.com/.../gg334418.aspx

maybe you can create 1 reoccurring bulkdelete job and find a query that will break it in chunks so it can run on a time that will not interfere with production.

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

I would strongly advise you do not update the database directly in this (or any other) way.

If you change the deletionstatuscode, the Deletion Service will try to delete these records and clean up after them (eg removing unnecessary rows from POA), and you have no control over how long that will take or any means to stop it if it overruns into production hours.

Use Bulk Delete to do this, in chunks as others have suggested. Time a good sized chunk and check the impact of the async job doing the Bulk Delete and the deletion service cleaning up afterwards.

Was this reply helpful? Yes No
Suggested answer

Hosk on at

Like (1)

Report

updating records directly on the database is unsupported and if it goes wrong Microsoft will only offer limited support. Sometimes the system updates other related records and tables, if you do this by directly on the DB this will not happen and you could find the database is in an odd state, which might cause problems later.

I would not advise doing this, particularly when you can do this over a number of nights using bulk delete

Was this reply helpful? Yes No