Using the most recent release of 5.6 CE, we recently added a report for a client which they access from behind security.  The report does a data dump for the client whose site generates a lot of database traffic (outside DNN) that they occasionally use for debugging what is going on.  The report runs against a very large and constantly active changing table, but it's paged so that the report only shows recent history first.  We used the REPORTS module to create the report.  Then we ran into an interesting (and very hard to diagnose initially) problem.  It turns out that the REPORTS module implements isearchable - on the entire content of the report (no matter how many pages).  Suddenly our search index had literally 4gb of data in it!  And the search index time shot up to over 3000 seconds every time it ran, and we had transaction logs in the 600mb range (we do TL backups ever few hours).



For now, and for this site, the search index module is disabled (searching isn't important on the site) but we looked and there's no way, even as host, to uncheck isearchable in the REPORTS module (other than altering the code and commenting out the isearchable interface), nor does there seem to be an exclusion option at the page, module or search admin level that says "don't index this page" or "don't index this module".  We now see why many companies go with a third party module for search.  Other than tinkering with the search admin or code does anyone know of a way to make DNN ignore some content for searching even if the module is marked isearchable.  Should it even be indexing stuff that's behind a security wall?



Cheers, Lee