I know deleting portals is most likely an edge case...but in multi tenant DNN instances it's a common practice to delete either expired portals or "test" portals, etc.  

Currently it's very common to get a SQL timeout when deleting a portal with even just a few pages and or users.   What's worse is that the deletion process is a big progressive and doesn't seem to be managed within a transaction.

For example, I recently attempted to delete a portal that had 265 users and 41 pages.  Procedurally I've learned to go into the portal and delete all of the pages manually (except for the homepage) then empty the recycling bin for that portal before attempting the delete from host | portals.

The first time through I received a SQL timeout error; users were down to 90 and page to 21.  Additionally all of the files had been deleted from the portals folder.

The second time through again I received a SQL timeout error; users were now 0 but pages remained at 21.

All subsequent attempts do not show any progress and the portal remains in the portals list although all pages, files, module have been removed laving the porta itself in a "half deleted" state.

I should point out that I'm running DNN 5.6.3 but I've experienced this on multi tenant environments going back a few years.  I was "cleaning house" so to speak as prep to upgrade to 6.02...but now I have a couple of portals in a strange state.  Not fun.

---

Steven Webster
Manager, Community Platform
F5 Networks, DevCentral

Thanks Cathal. I logged it.

---

Steven Webster
Manager, Community Platform
F5 Networks, DevCentral