→ VideoRunning a production Galaxy server, you some times end up in with a situation, where you manually need to interact with the database. e.g. you need to change the state of a job to 'error'. This is always a very risky adventure. Or a not-at-all risky situation: you want to extract usage information, which can not be gathered using the given report tools. For both cases, you need a good understanding of the Galaxy database schema. Learn some of the design concepts of the database, which parts of the schema are stable, and which will be changing in the foreseeable future. Also, some advice will be given on how to migrate a production Galaxy server running on MySQL to PostgreSQL.
Session Document
Prerequisites:
- Experience maintaining a production Galaxy server Basic knowledge of relational databases and SQL statements.
