We run a sql job regularly to purge our event logs and other logs to prevent them from getting too large.  We're using Sebastian's script (http://dnnscript.codeplex.com/releases/view/612643) to truncate the event logs and it works great. It allows us to manage log truncation from the database instead of the interface.  

If I run the SQL job to purge all the logs, this error goes away but then it reappears within a matter of hours or days.  It is most prolific on one specific host.  Please advise ... how can this be fixed in such a way where it doesn't return?

---

- GhostTruth.com

Thanks Joseph. That's correct, that's why we're using Sebastian's script to truncate the logs. It drops the constraints, truncates the table, and then recreates the constraints. We run this script on a schedule in a SQL job on our server. It gets the job done.

This error is a headache though as it is inundating our logs. Also we can't even view our Event log through the interface because the page throws this same error. We can only see the errors logged in there by going directly to the database. I am not a DBA but have been googling this ... would it just be a simple thing of dropping and recreating the constraint again? I can do that but would this prevent the issue from resurfacing the next time the truncate log job runs or is there more that needs to be done to kill the error completely?

---

- GhostTruth.com

When you said the cascade delete was on line 82 I went to check and noticed that it was on line 89 in our script. Apparently we were running an old version of your script. We had Version 0.9.8 (2015-03-19) but looks like the latest is Version 0.9.8 (2015-07-25) ... I've just updated it and will keep an eye out for anymore of these errors.

Thank you for creating this script by the way. Its come in so handy. Its nice to be able to schedule it and not worry about our database becoming obese ...

---

- GhostTruth.com