Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...SQL and SQL Ser...SQL and SQL Ser...truncating eventlog in dnn 3.4.1truncating eventlog in dnn 3.4.1
Previous
 
Next
New Post
10/13/2015 4:38 PM
 
If your schema is dbo and you are using an empty objectQualifier (i.e. the tables in your database are listed as dbo.Affiliates etc), the script should be able to run in SSMS without problem.
Would you mind to post the error message issued by SSMS, thank you.
PS: please make sure, compatibility level of your database is set to 2012 (right click database node and select database properties)

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/14/2015 12:05 PM
 

Weird I just cut and pasted the last sql statement that I put and said I was getting errors just to try again and this time it was success. Not sure the difference maybe I had an extra space somewhere but it seems to work now.  Thanks for your help.  By the way why was it that in my case I wasn't suppose to use ""- as an empty string for the object qualifier.

I do have one more question which I guess should be a different thread but was just wondering if you had a quick answer for it.  I have had issues with my dnn app continually recycling.  I did turn off all the time limits but discovered I missed setting the regular time interval under the recycling category to 0.

-----------------------------------------------------------------------------------------------------------------

I site I saw suggested setting the limit interval to o under CPU
The idle time out to 0 under PROCESS MODEL
Lastly regular time interval to 0 under RECYCLING.

--------------------------------------------------------------------------------------------------------------

But my question is this. One person said that they turned GENERATE RECYCLE EVENT LOG ENTRY > REGULAR TIME INTERVAL to FALSE.

I was wondering if that was really necessary or if it was another property needing to be tweaked to prevent app shutdown during idle moments without having to use a continuous pinging service that pings once every 5 minutes.

Another suggestion someone had was applying disallowRotationOnConfigChange or turning it to true or on but the question came up that even if you did this in order for it to really take the effect you were looking for you would need to do the following

---------------------------------------------------------------------------------------------------------------------------------------------

There is a File Change Notification (FCN) registry change that can prevent web.config changes from causing an appdomain recycle, but then the changes themselves won't be picked up either until the app pool is manually recycled..."

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

My question is would the above change be wise? It seems as though it doesn't really matter weather you turn it on or not in regards to preventing app shutdown if you have to manually recycle anyway to have a web.config change to be applied. It almost seems like in reality it wouldn't really be an asset since when you make a change in your web.config file you expect it to be applied so it is reflected in your dotnetnuke app so why would you want to turn it on just to be forced to manually recycle the app for it to apply when it would do so automatically otherwise.

 

Anyway if you could let me know if this registry key change is a good idea or would further help prevent unnecessary restarts I would appreciate it I feel if you are changing web.config having it applied to your live site is necessary but let me know what your assement would be I am using a vpn that I have full access to windows settings so I can do anything a full fledged web admin could do.  Thanks, Bo.  

 
New Post
10/14/2015 12:17 PM
 
I am glad it finally worked for you, "" was just meant to be an empty string (I just put the quotes around, because otherwise it is hard to distinguish from a space.

If your site recycles frequently, you should uncheck "recycle after 1740 seconds of inactivity" in "recycle options" of your IIS Application pool. We usually recycle at 03:00 AM once a day and after the site hit its resource limits. You should tweak other IIS settings only, if definitely needed.

FCN should be configured in your Web.config by DNN, you should tweak this only if needed (usually a recycle makes sense after modifying web.config or other code files.

If you are having performance issues, I would start uninstalling all DNN extensions you don't need (make sure to enable "delete files"), i.e. unused modules (except DDR Menu), providers and skins.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/15/2015 2:10 AM
 

I think I now have the optimizations I want I did think it was a good suggestion in regards of forcing the site to recycle at least once a day at night in order to flush out anything that may have gotten stuck somehow throughout the day. So hopefully with all my tweaks in iis the pool should only recycle for two reasons when it is scheduled to do so once a day and when making edits to the web.config file as I did not mess at all with the property that would stop dnn from recycling upon web.config changes as I want any changes made to the web.config file to be applied via recycling the app but other than those two exceptions I would think that the site would not unload hence the users for the most part will experience a fairly quick website except of course that lucky user that hits it after that magic number of 3:00 AM when the pool recycles but other than that it should stay good and solid since I would be hitting it right after a web.config change to make sure it all operated properly so really it will only be slow for the one person a day who firsts visits the site after the scheduled recycling happens and for that I do thank you for your exceptional help here despite the fact that my last question was really irrelevant to the discussion of this thread thanks for taking the time to address it anyways

 

Regards,

 

Bo

 
New Post
10/15/2015 4:38 AM
 
Bo,
I am glad you got your solution. You may establish an external monitor (there are several services available), which pings your site e.g. every 15 minutes, this should eliminate the initial wait for the first visitor in the morning as well.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeDevelopment and...Development and...SQL and SQL Ser...SQL and SQL Ser...truncating eventlog in dnn 3.4.1truncating eventlog in dnn 3.4.1


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out