Hi Hugh, the database upgrade steps are as easy as running an SQL file. The only obvious thing that can go wrong is that you don't run them in the correct sequence. I personally haven't ever encountered any problem with this procedure.
So, with postgres, log in as your dspace user and run psql dspacedbname < /path/to/database_schema_15-16.sql psql dspacedbname < /path/to/database_schema_16-17.sql psql dspacedbname < /path/to/database_schema_17-18.sql psql dspacedbname < /path/to/database_schema_18-3.sql Where dspacedbname is your dspace database name (usually "dspace"). You have to do that on a DSpace 1.5-format database, obviously, so do a psql_dump of your production database, drop all tables in your testing database, run psql dspacedbname < production_dump.sql, then do the schema upgrade steps, then start DSpace 3.0 pointing to it. Really, try it, it's very simple and you have to actually try it on your testing server to gain the confidence. The assetstore will work without changes with any DB schema version (between 1.5 and 3 I'm certain of it). I can't really think of anything that could go wrong, but if it does, you can ask here. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
