Last post 12 hours 41 min ago

Posts last week 94

Average response time last week 34 min

All time posts 67911

All time tickets 10496

All time avg. posts per day 20

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#1389 – Table in SQL taking 200+ mgb...

Posted in ‘sh404SEF’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Monday, 16 November 2015 09:51 UTC

Liberty

Hi there!

We switched at some point the URL creation recording, and forgot to turn it off...
now we turned it off, but there's still a huge table of 200 mgb - view in pic - i'm asking if it's ok to clean this table if the url creation recording is turned off..

and a suggestion, to add some kind of purge button, or delete button for this.
looking forward to hear from you,

thanks,

Joe

Monday, 16 November 2015 09:58 UTC

wb_weeblr

Hi

It seems you have enabled the "Record URL source" feature, which is a debugging feature and should not be used in production. This is why, when it's enabled, you have a big orange warning on the main control panel.
If you don't use this feature any more, you can indeed delete the content of the table.

Currently, deletion of this data is done:

- on a per URL basis (button "Delete details" in popup)
- globally, by using the Purge button,which will also delete all automatic URLs, but can cause some 404s.

As this is debugging feature, it's really meant to be used by developers, and so purging directly in DB is fine.

Rgds

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.