SQL To Determine Which DNN Modules Are Not Being Used > Venexus, Inc.

SQL To Determine Which DNN Modules Are Not Being Used By Jeff Smith

Tuesday, October 07, 2008 12:03 PM :: 528 Views :: 3 Comments ::

We perform a lot of DotNetNuke upgrades. Sometimes we see sites that are very old (recently did a DNN 2.0 upgrade), that have a lot of 3rd party or custom modules installed. Many times, these modules are not being used. So, to eliminate any possible upgrade issues, we will unistall any modules that are not being used. Here is the SQL for determining which modules that are installed that are not being used:

SELECT     ModuleDefinitions.ModuleDefID, ModuleDefinitions.FriendlyName, ModuleDefinitions.DesktopModuleID
FROM         ModuleDefinitions LEFT OUTER JOIN
                      Modules ON ModuleDefinitions.ModuleDefID = Modules.ModuleDefID
WHERE     (Modules.ModuleDefID IS NULL)

By John Henley @ Friday, October 10, 2008 8:09 AM

This SQL is not inaccurate. In fact, it highlights your own VenexusWebControls, which I know I have in use.

By Jeff Smith @ Friday, October 10, 2008 9:34 AM

You have the module installed on a page? Anytime a module is added to a page, it is references in Modules table, so I am confused to why it is showing.

By John Henley @ Friday, October 10, 2008 9:54 AM

I do indeed have VenexusWebControls installed on a page.

Some of the other ones that this SQL shows are supporting modules which don't get installed on a page, but are definitely used and should not be uninstalled.

For instance, "PageBlaster", "metaPost", "UCanUse.Core", and (interesting) "UsersOnline".

So I think you need to say "this SQL shows modules which could *potentially* be removed, but investigate their use (or lack of use) before removing them.

Comments

Only registered users may post comments.