If you intend to keep current with PEQ's updates, here's how I'd do it:
Code:
UPDATE zone SET min_status = 255 WHERE short_name = 'abysmal';
UPDATE zone SET min_status = 255 WHERE short_name = 'acrylia';
UPDATE zone SET min_status = 255 WHERE short_name = 'akheva';
UPDATE zone SET min_status = 255 WHERE short_name = 'anguish';
UPDATE zone SET min_status = 255 WHERE short_name = 'apprentice';
UPDATE zone SET min_status = 255 WHERE short_name = 'arcstone';
UPDATE zone SET min_status = 255 WHERE short_name = 'arena2';
UPDATE zone SET min_status = 255 WHERE short_name = 'arttest';
UPDATE zone SET min_status = 255 WHERE short_name = 'ashengate';
UPDATE zone SET min_status = 255 WHERE short_name = 'atiiki';
Start plugging in zone names and replace the 255s with 0s. Once you have a nice big list, save it into a file called custom.sql. Then you can source in your customizations every time you update to the newest PEQ database.
The way Weldarr told you is fine if you either 1) plan with sticking with the version of the database you have indefinitely or 2) you don't mind doing it that way every single you time you update. Thought I'd give a bit of a pointer on how to do it the 'hard way', which will wind up saving you time in the long run.