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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SearchItemWordPosition table takes up most of the databaseSearchItemWordPosition table takes up most of the database
Previous
 
Next
New Post
12/7/2011 6:19 PM
 
Support Novado wrote:
Sebastian,

We suffer the same issue (5.6.1).

The merge statement you've mentioned above does not appear in die stored procedure of the DNN 6.X database. Is it solved there?

So we just have to replace the INSERT statement with the MERGE statement?

Kind regards

 yes, please give it a try


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
4/16/2012 2:41 PM
 
Sebastian Leupold wrote:

you may use this procedure to clear your search tables.

I am investigating the current behaviour.

 Would it not be better to drop the tables, rather than delete them, so that the deletion of the potentially millions of records is not logged?

It seems to me that it would be best practice, in this case, to drop the tables.

truncate table {databaseOwner}{objectQualifier}SearchItemWordPosition
DROP {databaseOwner}{objectQualifier}SearchItemWord
DROP {databaseOwner}{objectQualifier}SearchWord
DROP {databaseOwner}{objectQualifier}SearchItem

 
New Post
4/16/2012 6:58 PM
 

I wouldn't recommend dropping any tables that'll cause issues if you don't get them properly recreated. I would recommend truncating if possible


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
4/17/2012 3:09 AM
 
tables with existing foreign key constraints cannot be dropped or truncated, but you may drop the constraint, truncate the table and recreate the constraint. You need to ensure after every DNN upgrade, whether the contraint definition has changed and you need to adopt your re-creation statement for it.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/26/2013 9:26 AM
 
Hello,

I have the same issue, version of dnn is 06.02.03.

I cleared the search tables but are refilled quickly.

It's the same thing that happens to Mark, I have duplicates by position.

Many thanks.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SearchItemWordPosition table takes up most of the databaseSearchItemWordPosition table takes up most of the database


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