Use of SQL Query Executor

[DrByte]

That would also require taking the site off line which I would rather not.

That's what test sites are for.
Given the amount of altering you're doing on a daily basis I'd think it would be very prudent to have a complete copy of your site in another database specifically for testing these kinds of things.

Complex? no, they are simple but 9,000 of them. It's a simple question that if it worked I still wouldn't know the answer to. To save time though will it run a batch of 9,000 inserts and updates and drop tables and create tables and simple queries to repopulate these table (these are NOT package tables but a reformatting a copy of them for other use). And, here's the untestable question, (see above) as 1 transaction so an abort part way through results in a rollback?

Frankly I've never had a cause to do that using the SQL patch tool. It's designed for "patches" (hence the name).
But in the main it really just executes queries ... so I suppose if you write the query as a "transaction" then it would naturally rollback if the "transaction" failed.

And, if you read my last post all the way through and click the Help link I mentioned, you'll see that there is guidance there on giving guidance to treat multiple "statements" as one batch query.

Again, testing is prudent. Use at your own risk.

I might suggest that what you really need is a desktop tool like SqlYog or Navicat, especially if your hosting company can't provide a reliable way to run the entirely industry-standard phpMyAdmin tool.