I'm a bit blown away by the response to this question. I was trying to use the search results feature until I also realized, what I consider, a bad idea of using the module title instead of the page title on results. However, I then noticed that if you have two HTML Modules on a page, it returns that page twice! This seemed like a bad idea, as well. Kind of ruined the point of the relevancy, I would think.
Anyway, while looking into it, I found this view in the database: vw_SearchItems
This view seems to be part of what DNN uses to feed their search results. I didn't go into too much depth in figuring out the ins and outs of this view or what it gets its data (it seems a lot of it has to do with some kind of stored procedures).
At first, I thought about altering the view to just pull in a Tab-Name, but I'm not sure if updating DNN would overwrite my change. So, I decided to just make my own custom module for search results using their Search Items table. I'm not sure if this is an amazing idea or not, but it seems to be working for now.
This query should work just find if you have SQL 2008;
SELECT TabName, TabID, TabPath,
Text = Stuff((SELECT '' + [Description]
FROM vw_SearchItems WHERE vw_SearchItems.TabID = Tabs.TabID FOR XML PATH('')),1,0,'')
FROM Tabs WHERE (Stuff((SELECT '' + [Description]
FROM vw_SearchItems WHERE vw_SearchItems.TabID = Tabs.TabID FOR XML PATH('')),1,0,'')) IS not null
AND IsDeleted = 0 AND IsVisible = 1 AND IsSecure = 0 AND EndDate >= GETDATE() AND StartDate <= GETDATE()
AND PortalID = 0
PortalID can, of course, be changed. Also, this was done with DNN7.
If anyone has any other input on this query or another way to approach this, I'd love to hear it.