On 3/21/2014 1:42 PM, David Lerer wrote:
> Frequently, we import a production dump that contains only 1 or 2 databases into one
> of our QA instances that contains many more databases. (i.e. "database" being a "schema"
> or a "catalogue).
> At the beginning of the import script, we first drop all objects in the QA database
> so that it will be a perfect match (object wise) to production.
> Is there an easy way to lock the whole database for the duration of the import - so
> that no developers can update the database?
> Obviously, I can revoke permissions, but I was wondering whether there is a better
If you start with a DROP DATABASE xxxx that will pretty much ensure
that nobody gets back into it.
Then re-create your tables in a new DB (yyy)
As a last set of steps do
CREATE DATABASE xxxx
RENAME TABLE yyy.table1 to xxxx.table1, yyy.table2 to xxxx.table2,
.... (repeat for all your tables).
DROP DATABASE yyy
Because this is essentially a metadata flip, the RENAME will be quite
MySQL Senior Principal Technical Support Engineer
Oracle USA, Inc. - Hardware and Software, Engineered to Work Together.
Office: Blountville, TN