then I suggest best practices is not to do it till a release.
as your db gets larger the processes of verifying everything can take
weeks or months.
do your testing against a copy of your production.
=========================
BJ Freeman <http://bjfreeman.elance.com>
Strategic Power Office with Supplier Automation
<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com <http://www.specialtymarket.com/>
Systems Integrator-- Glad to Assist
Chat Y! messenger: bjfr33man
Matt Warnock sent the following on 8/30/2010 5:28 PM:
Thanks, BJ, but I am looking for best practices on how to do it NOW, not
the automated component under design for the future. The emails you
mentioned don't really address any of the questions below. But neither
does any of the existing docs I have found so far. :-)
Pointers, anyone?
I did try "./ant run-install-seed" on an existing database (previously
created with "run-install"), it ran without obvious errors and the
number of rows changed that it reported was several thousand, but less
than the number with "run-install".
So can it (usually) be safely run on a production database, and will it
have the intended effect of updating the seed data (if necessary)
without deleting/overwriting the production data that may refer to that
seed data? From previous database experience, I know that
updating/removing/replacing data to which other data points is often a
problem, to say the least.
Also, are there any pros and cons for putting the OLAP datasource in a
separate database from the main data source? The existing derby demo
uses two, but most of the setup tutorials I find are pretty vague on
this point, but if I point both data sources to the same postgresql
database, I see no obvious errors. Am i asking for trouble down the
road? What is the difference between the two, and are there data
collisions I'm not seeing yet?
