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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...What am I doing wrong?What am I doing wrong?
Previous
 
Next
New Post
9/11/2007 3:39 PM
 

Several hours after going live with my site, I got an email to an old email account I hardly ever use anymore about excessive database usage. Apparently, my webhost, (starts with an L and rhymes with dunarpages) missed my requests to not use that as my primary (or in this particular case, only) point of contact, and also, saw nothing wrong with just deactivating my domain without any warning or secondary attempt to contact me, despite the fact that they do have other email addresses and two phone numbers on file. Anyhow, here's the email I got...

 

During a routine check of the MSSQL server Castor this morning it was discovered that your database was using excessive resources on the server. Since the MSSQL server is a shared resource that provides database services to several of our shared Windows servers we simply can not allow a single database to monopolize on the server resources as that interferes with other databases and prevents those same services from being available to other databases. As such your domain letzgoout.com has been suspended. You will need to address this issue immediately to prevent further action against your account.

You database had over 127,000 reads and 132,000 writes and has the highest activety on the server. You will need to address the coding issues that are causing this resource usage and if you are unable to correct it you will need to look into upgrading to a dedicated server. It appears that there is a query that is looping and that is contributing to the resource usage. The query is provided below:

delete from dbo.SearchItemWord where [SearchItemID]=@SearchItemID

There have been 459 executions of this query in 90 seconds. This is excessive usage of the database services and is part of your overall resource usage that you will need to address.

--
Best Regards,
(the guy who nuked my account and was kind enough to send me an email to an old address, to tell me that they had done so, then ignored 4 hours of support ticket submissions by me trying to find out why my account was deleted)

 

 

So, my question is, why would so many hits to that database be made? I'm guessing it's a search indexing function, but maybe I'm wrong. Is this normal, is it because the site just got posted, or is there something configured wrong? Anybody else ever have this problem in the past?

 
New Post
9/11/2007 5:38 PM
 

check the scheduler for frequently called actions, this query is not called by core framework and should not be called frequently by any module.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/11/2007 7:05 PM
 

oops, during further investigation I noticed, that this statement is called for each updated search item, i.e. text/HTML module, announecment module etc. if it was called that often, either you did a lot of work, ore there are modules, that misimplemented the search interface, causing to re-index all entries each time the indexer runs. incresing time between index runs may leverage the issue, but not solve it. try to identify the misbehaving module and contact the developer.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/11/2007 7:12 PM
 

Thanks for the tip. DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE, which was my primary suspect runs every 30 minutes, which I think was its default setting. DotNetNuke.Entities.Users.PurgeUsersOnline, DOTNETNUKE runs once a minute, but I can't imagine that does anything like what the host claims they saw. And even if it is the cause, unless I disable it completely, it sounds like whatever the process at fault is only needs to run once to get these guys to kill my site.

I have one module that has a table with about 40k records but it does not implement iSearchable. Could that still be the cause, and if so, is it a one time thing, since the site did just go live on that server or is that something I should be looking deeper into?

Or should I just be looking for another provider? I've had other problems with them in the past, and doing a little research, I see that I am clearly not alone. I've been waiting over 8 hours just to talk to somebody that can address the issue. I'm refocusing my efforts to finding a new host.

Anyone got suggestions?

 
New Post
9/11/2007 7:14 PM
 

Thanks even more!

Unfortunately, you're talking to the developer.

I'm guessing it is that module with the 40k records, but, first, would it index it at all without implementing iSearchable, and if yes, would it reindex it entirely every time, or just new records?

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...What am I doing wrong?What am I doing wrong?


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