Support Forum

Mr P. said
those are wp tables...

That's what I thought, just needed to confirm we weren't missing some tables!

Yellow S. said
It is probably pretty safe...

Thanks again for the feedback. I ran these queries, and was able to reduce the size of the sfmembers table, but only by about 8MB. Think I'll quit while I'm ahead. but every little bit counts, eh?

Good luck keeping the WP transient rows under control in the options table!

I hear ya there! Our wp_1_options had grown to 60+ MB. I got it down to 1.5 MB using the following...

DELETE FROM `wp_1_options` WHERE `option_name` LIKE ('_transient_%');

Finally, should at some point we decide to clean out the wp_users I've now deleted from sfmembers, would this do the trick for me in bulk?

DELETE FROM wp_users WHERE user_id
NOT IN (
SELECT user_id
FROM wp_1_sfmembers
)

Thanks again! I really appreciate all the hand-holding through this.

Yellow Swordfish said:

That query should work OK against the users table.

I wanted to review these users before deleting them. But when I run this query:

Select * FROM wp_users WHERE user_id NOT IN ( SELECT user_id FROM wp_1_sfmembers )

I get the following error:

#1054 - Unknown column 'user_id' in 'IN/ALL/ANY subquery'

I have confirmed, however, that the user_id column does indeed exist in wp_1_sfmembers. Any thoughts?

There is NO user_id column in the WP users table. It is named 'ID'...

Thank you! Query works that way.

Sorry for the late reply, still banging our heads here trying to nail down the case of our recent MySQL issues. This will help us continue housekeeping in the meantime.