Hi,

We are running DNN 4.9.0 with the latest DSlocalizator. With the Tablocalization box checked, it immediately causes the SQL Activity Monitor to show that the following is being executed 67,000 (!) times a minute:

SELECT
[TabId],
[LocaleKey],
[TabName],
[TabTitle],
[TabDescription],
[RedirectTo],
[RequireSSL],
[IsVisible],
[DisableLink],
[KeyWords],
[SkinSrc],
[ContainerSrc],
[Url],
[IconFile],
[SqlViewState],
[UseWhiteSpaceRemover],
[AdminSkinSrc],
[AdminContainerSrc],
[LogoFile],
[AdjustSqlSession],
[AntiSessionExpiration],
[AntiSessionExpirationTime]
FROM Delisoft_TabLocalization
WHERE
[TabId] = @TabId
AND [LocaleKey] = @LocaleKey

There are about 250 tabs in the install total, and only around 40 localized variants of the tabs. 7 different lanaguage/locales are present in the install.

Any help would be hugely appreciated!

Thanks, we have tried with the cache set on and off and it does not really seem to have an effect. Can you say by what mechanism it is cached? Memory, file, viewstate etc.

Is there any means to override the 'new tabs' check, if that is likely the source of all the SQL overhead?

I just tried on two DNN instances and the cache worked fine so I don't know what could be happening in your own installation.

I don't make profit from this module so my intention is not to force people to buy the source. Some people buy it because the want to be sure to have the option of custom programing if my site goes off line forever (Hope my site will keep forever working).

The cache option was created when I saw the same behavior your are seeeing now and it works for me a many people using it. The cache is the standard cache object included with DNN

What version of DNN are using?

What version of DSLocalizator?

Is the cache option activated on you host settings (DNN HOST SETTINGS)?

The cache option I was refering in my previous post is the one inside the HOST options in the DSLocalizator module. It is just a siple checkbox. Are you sure that it was activated?