It can be found in the DNN460_Install package. Extract the package and check the "Install" directory.

I already submitted this to Bug Tracker (DNN-6303) a few days ago. you can replace ALL the 'dnn_ ' with {databaseOwner}{objectQualifier}. Re-zip the file and install it again.

It should look like the following:

/************************************************************/
/*****              SqlDataProvider                     *****/
/*****                                                  *****/
/***** 08/13/2007 sleupold: added                       *****/
/*****                                                  *****/
/*****                                                  *****/
/***** Note: To manually execute this script you must   *****/
/*****       perform a search and replace operation     *****/
/*****       for {databaseOwner} and {objectQualifier}  *****/
/*****                                                  *****/
/************************************************************/

/* initialize new settings value for existing modules: */
INSERT INTO ModuleSettings (ModuleID, SettingName, SettingValue)
SELECT     {databaseOwner}{objectQualifier}Modules.ModuleID, N'TEXTHTML_ReplaceTokens', 1
FROM         {databaseOwner}{objectQualifier}Modules INNER JOIN
                      {databaseOwner}{objectQualifier}ModuleDefinitions ON {databaseOwner}{objectQualifier}Modules.ModuleDefID = {databaseOwner}{objectQualifier}ModuleDefinitions.ModuleDefID INNER JOIN
                      {databaseOwner}{objectQualifier}DesktopModules ON {databaseOwner}{objectQualifier}ModuleDefinitions.DesktopModuleID = {databaseOwner}{objectQualifier}DesktopModules.DesktopModuleID
WHERE     ({databaseOwner}{objectQualifier}DesktopModules.ModuleName = N'{databaseOwner}{objectQualifier}UserDefinedTable')

/************************************************************/
/*****              SqlDataProvider                     *****/
/************************************************************/

sorry, this was an unforgivable oversight of me, I will take care, it gets corrected in next module version (that shall get rid of legacy limited token replace). However, the upgrade script only defaults settings of existing modules from "no TokenReplace" to "limited TokenReplace", in case anyone used the previous tokens, that had been introduced but never documented AFAIR, therefore i expect very few users are affected.