[Plugin: Backup Scheduler] Feature Request – DROP TABLE IF EXISTS

WP-DBManager for instance has DROP TABLE IF EXISTS statement in it’s backup sql so it can restore over existing tables.

Thank you for your time and effort.
I look forward to giving it a test run.

Just did,sorry to take so long.
My first test failed.
It appears the drop table succeeds, but before you can insert into a table that has been dropped you must have a Create table command to recreate the table.
For instance a typical phpmyadmin export has the lines:

DROP TABLE IF EXISTS'wp_commentmeta';
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE 'wp_commentmeta'

Please nor I have replaced sql backticks with single quotes so I can post it.

[ Moderator Note: Please post code or markup snippets between backticks or use the code button. ]

No I do not.
Here is the start of a backup for a single site in a multisite install.

-- -----------------------------
-- CREATE wp_3_commentmeta
-- -----------------------------
DROP TABLE IF EXISTS wp_3_commentmeta;
;

-- -----------------------------
-- CREATE wp_3_comments
-- -----------------------------
DROP TABLE IF EXISTS wp_3_comments;
;

-- -----------------------------
-- CREATE wp_3_links
-- -----------------------------
DROP TABLE IF EXISTS wp_3_links;
;

-- -----------------------------
-- CREATE wp_3_options
-- -----------------------------
DROP TABLE IF EXISTS wp_3_options;
;

-- -----------------------------
-- CREATE wp_3_postmeta
-- -----------------------------
DROP TABLE IF EXISTS wp_3_postmeta;
;

-- -----------------------------
-- CREATE wp_3_posts
-- -----------------------------
DROP TABLE IF EXISTS wp_3_posts;
;

-- -----------------------------
-- CREATE wp_3_term_relationships
-- -----------------------------
DROP TABLE IF EXISTS wp_3_term_relationships;
;

-- -----------------------------
-- CREATE wp_3_term_taxonomy
-- -----------------------------
DROP TABLE IF EXISTS wp_3_term_taxonomy;
;

-- -----------------------------
-- CREATE wp_3_terms
-- -----------------------------
DROP TABLE IF EXISTS wp_3_terms;
;

-- -----------------------------
-- INSERT INTO wp_3_commentmeta
-- -----------------------------

-- -----------------------------
-- INSERT INTO wp_3_comments
-- -----------------------------

INSERT INTO wp_3_comments VALUES(1, 1, 'Mr WordPress', '', 'http://theme.dev/', '', '2012-08-23 12:33:55', '2012-08-23 12:33:55', 'Hi, this is a comment.To delete a comment, just log in and view the post's comments. There you will have the option to edit or delete them.', 0, '1', '', '', 0, 0);

I just ran used backup scheduler on a single site wordpress installation on the same server and it created a good backup file as in your post Arffff …
The installation which is not creating good backup sql is a multisite installation on the same server. Server is Lamp with cPanel MySQL 5.0.92 PHP 5.2.17.
The instalation is on a multi db (16 database), which is most likely the cause of the problem.
I should have listed full environment in my first post. Sorry.

I have just tested two versions of this multisite installation on my local development server. It is a xampplite server on windows.

First was using the original single database version from before I migrated the data to the multi database. Backup scheduler created a good backup sql for a single site in the multisite install.

Next I tested the same installation but this time with the multi database connection. Backup scheduler created broken sql as I posted above with missing create table sections.

So that is two separate multi database installations giving problems, one on a Development and one on a Production server. I am using the multi-db plugin from wpmudev when I connect to the multi databases.