Can't update using DBUpdate-to-2.3.mysql.sql

I'm trying to figure out why I can't update an otrs DB that I've moved over from an older otrs server. I've followed all the steps as seen in http://faq.otrs.org/otrs/public.pl?Action=PublicFAQ&ItemID=258 and http://faq.otrs.org/otrs/public.pl?Action=PublicFAQ&ItemID=259 I've gotten as far as importing the sql dump from the old server into the new server, and I'm now trying to update the schema. The old server was running otrs 2.2.4 and I have the new 2.3.1 on the new server. So, Ias I understand it, I only need to user DBUpdate- to-2.3.mysql.sql. But here's what happens when I get there: bash-3.2# mysql -p otrs < /opt/otrs/otrs-dump.sql Enter password: bash-3.2# mysql -p otrs < DBUpdate-to-2.3.mysql.sql Enter password: ERROR 1050 (42S01) at line 8: Table 'users' already exists Can someone tell me if I'm missing a step somewhere that's not shown in the FAQ? Thanks, Will

I'm interested in locating other companies using OTRS in the same field we are in. We are a small IT services shop, and as such, don't have the manpower on staff to dig in and tweak OTRS. I'd love to chat with someone about how you use OTRS, what workflow you've implemented and any customizations you've made. Obviously, it is your expertise in customizing OTRS we're looking for, so if you have developed some customizations we would like to implement, I'm definitely not above paying you for your time! As a business model, we have scheduled maintenance visits to client locations that we perform. During those visits, we work on any number of tasks. Each task we work on for a client should be a ticket. Sometimes we also perform remote work and unscheduled work. As far as billing, we typically bill for the visit, and not for each task. So we don't really use the "time units" in the tickets in OTRS, as they don't have a lot of meaning for us. So I am looking for how others have integrated time tracking with ticket tracking. Based on suggestions of others here, I am looking at tying together a timesheet type package with OTRS (currently evaluating Timetrex and a few others). Obviously, if you are in the same geographical location as me, you might not want to share these "secrets" with me, and I understand. I am in the Salt Lake City, Utah, area, so if there is anyone who would like to share how they've implemented OTRS in this type of business, please let me know! Feel free to drop me a line off the list as well, as this might not be 100% pertinent to others here.
participants (2)
-
Aaron Spurlock
-
Will Matthews