1

after trying to use content staging websites to no success and finding them buggy, we removed them.

I've noticed in the database, there are a lot of tables prefixed with s_ . I believe these tables were created when we creating new staging or store sites called Staging.

They are taking up a lot of room. Our DB is about 8GB and without the extra tables, it would be a bit under 2GB.

Is it safe to just go into phpMyAdmin and drop the tables?

I have tried this on a development server and everything seems ok but I am wondering if there are any gotchas I am not uncovering before I do it to the production database.

Thanks

3

If this is a production site, I would proceed with caution.

I would first back up the database

mysqldump -u [username] -p [db name] > db.backup.file.sql

I would then drop the tables, do testing on the site, and if everything is working as expected, then you are likely in the clear, however, if everything is not ok, then you will need to drop the database, create the database, and import the backup

mysql -u [username] -p -e "DROP DATABASE [db name]; CREATE DATABASE [db name];"
mysql -u [username] -p [db name] < db.backup.file.sql

Make sure the user you are using is capable of dropping and creating databases before proceeding.

  • Testing seems to be going ok. I'm going to set up and replicate and another server and have more people test next week. Also going to reach out to Magento for comment. – bones May 3 '13 at 20:50
  • Magento said the same thing. They thought it shouldn't be an issue but to backup first. I'm surprised they leave the junk tables in the database when you remove the staging sites, I don't see the reason for that as it takes up a lot of space. Either way, I removed the tables last week and have had no issues. – bones May 21 '13 at 19:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.