I've updated my OTRS install from 1.3.2 to 2.0.0b1 (mmm, bleeding edge). I noted the following errors during the database update, using PostgreSQL. I've attached the full log of the SQL update output so you have context as well. [...] ERROR: column "o" does not exist ERROR: column "escalation_start_time" contains null values [...] ERROR: column "comments" of relation "ticket_state_type" does not exist [...] This database has been upgraded through numerous OTRS versions (starting with 0.5b :), so it's entirely possible there's some strangeness with the schema that needs tweaking. If so, please advise. If not, there are bugs in the script. Otherwise, everything looks OK so far... Thanks, Bryan