Re: [Treebase-devel] TreeBASE migration project: data migration

[Mark D. <mjd...@ge...>]

Hilmar Lapp wrote:
> For software projects such as TreeBASE it is best practice to manage 
> versioning of the schema as you manage versioning of the software, and 
> to change a schema by writing and applying a migration script.

Okay, that makes sense to me.  Thanks.


> 
> The deliverable that we want from this is a fully scripted process 
> that takes the dumps from DB2, does its thing, and at the end the data 
> is fully imported into the NESCent PostgreSQL instance. The reason is 
> that we want this to be repeatable. I.e., we will test first, fix, 
> rerun, etc, until we can switch over in a well-coordinated fashion that 
> involves only minimal downtime.

Very good.  What do you think I should do first?

> 
>> [...] I would not like to perform the TB1->TB2 migration a second 
>> time, if at
>> all possible.
> 
> That would be a bad idea indeed once data have been added to TB2.

I think we were hoping to move from SDSC to NESCent before TB2 opened 
for business.  That is, we have an installation at SDSC now which is 
suitable for beta-testing, but I think we planned to discard all data 
uploaded by beta-testers before moving the data to NESCent.