I've currently got a 'test' database for developement (on the local
machine), plus the 'live' database which is out there in the world (and
soon, it will indeed be LIVE!).

I will be both adding new tables, plus (undoubtebly) be modifying
existing ones. Also, after creating new tables, I'll surely be
populating them - and sometimes that seems to be a long, iterative
process (import, check, drop, recreate, import again).

And I'm worried about snafu's occuring - trying to replicate things
perfectly.. but missing important steps along the way.

Just wanted to know how others minimize problems. Maybe the whole
notion of keeping the 'test' database is not a good one ? Maybe I shoud
ONLY use the DDL up on the 'live' database - then after its working,
just GBAK the 'live' one up, and restore it on my test machine (where I
only use it to test DML from my application)??

Thanks in advance for your thoughts.

[if you do all design work up front, and never peform modifications as
the project develops, please disregard the post !]


Rich Pinder
USC School of Medicine