Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql Admin > Re: Dev Process
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 2 of 2 Topic 4925 of 5549
Post > Topic >>

Re: Dev Process

by hhall1001@[EMAIL PROTECTED] ("H. Hall") Apr 22, 2008 at 07:05 AM

Medi Montaseri wrote:
> Hi,
>
> I was wondering if you could critique the following DB application 
> development process.
>
> Given a production DB and a Dev DB:
> 1- Develope schema and code on Dev including test data which will 
> impact sequences, etc
> 2- Dump the schema only (not the data) from Dev and restore it into 
> the production DB
> 3- Populate DB with real data, usage begins
> 4- Enhancement to schema on Dev DB including unit testing again with 
> impact on sequences
> 5- Dump schema and move to production
> 6- Goto 4
>
> Thanks
> Medi
>
>
The first problem is that you will have to take the production DB down 
to update it. Another problem with this method is that if you encounter 
problems while restoring data, then the down time could extend farther 
than your plan. Problems reloading the data can arise from new 
constraints etc. Finally,  you should consider testing the application 
program(s) as part of your update process.

A better plan might be to:

- Use only script files to update the dev server and use the same script 
files to update the test server (described below) and the production
server.

- Keep a log of changes to the dev and production servers. This shows 
when the script files were run on each server and gives you a quick view 
of the state of each.

- Use a third server, a test server to test the update prior to updating 
the production server. The test server schema should be at the same 
state as the production server, prior to the update. Update the test 
server using the script files and test your applications against it. 
Then update the db server.

The log let's you see what needs to be done. Use of the script files 
gives you the repeatability you need. Updating the test server first 
gives you the validation you need without the heart attacks.

The test server can be very light, i.e. anything that will run postgres.

--cheers
HH


H. Hall
ReedyRiver Group LLC
site: reedyriver.com



-- 
Sent via pgsql-admin mailing list (pgsql-admin@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
 




 2 Posts in Topic:
Dev Process
montaseri@[EMAIL PROTECTE  2008-04-18 11:52:57 
Re: Dev Process
hhall1001@[EMAIL PROTECTE  2008-04-22 07:05:12 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Sat Nov 22 17:17:58 CST 2008.