[ensembl-dev] exporting mysql DB sql and txt files

Baxter, Laura Laura.A.Baxter at warwick.ac.uk
Thu Jan 9 11:44:09 GMT 2014


Thanks for all replies, that all makes sense in the context of keeping data error free and ease of transfer.
Much appreciated, task now done!
Laura
________________________________________
From: dev-bounces at ensembl.org <dev-bounces at ensembl.org> on behalf of Paul Linehan <linehanp at tcd.ie>
Sent: 09 January 2014 10:10
To: Ensembl developers list
Subject: Re: [ensembl-dev] exporting mysql DB sql and txt files

(sent to individual address and not list)


Hi Laura,


> The ensembl ftp server provides the mysql databases as a DB schema (a
> *_core_x_x.sql file), then the contents of each table as a *.txt file - i
> think this is probably done for size reasons on large databases.


It also makes sense in the context of an error occurring. If you're loading
an entire database and something burps - you could be in big trouble, not
knowing exactly what failed or where. The drawback is more babysitting
and keystrokes.


The one *_big_* advantage of loading a database table by table is that you
can see any errors as and when they arise and localise them easily - at
least IMHO. Be sure to put a "COMMIT; " after every table data upload.


HTH,


Paul...



--

linehanp at tcd.ie

Mob: 00 353 86 864 5772

_______________________________________________
Dev mailing list    Dev at ensembl.org
Posting guidelines and subscribe/unsubscribe info: http://lists.ensembl.org/mailman/listinfo/dev
Ensembl Blog: http://www.ensembl.info/



More information about the Dev mailing list