I am not sure if this is an RT thing or if I should post it to MySQL & PG
lists instead, but I’ll start here.
I am currently about to trial RT in my office. Presently, to track jobs
we’re using a clunky old access DB. How hard will it be to import this
into my new RT database (either MySQL or PostGreSQL at this stage…) ?
Has anyone done such a thing? I couldn’t find anythign that might be
useful anaywhere… Is it hard to make all the right fields end up in the
right place, etc?
I am not sure if this is an RT thing or if I should post it to MySQL &
PG lists instead, but I’ll start here.
I am currently about to trial RT in my office. Presently, to track
jobs we’re using a clunky old access DB. How hard will it be to
import this into my new RT database (either MySQL or PostGreSQL at
this stage…) ?
I don’t understand what your describing. It sounds like you:
have some system based around access that tracks things
you’d like to start using RT
you want to import the data from your access system to RT.
If that’s, in fact, what’s going on, the databases are completely
irrelevant. RT (like every other system out there) uses its own
database schema and isn’t going to be able to read whatever your using
now.
You need to install RT, than write an import script that reads your
old data, and uses the RT api to create new data. You should be able
to crib the RT section off some of the other import scripts in
contrib, but I expect your on your own for the access part. You could
also hire someone to do it for you.
I couldn’t find anythign that might be useful anaywhere… Is it
hard to make all the right fields end up in the right place, etc?
you probably can’t find anything, because the solution is unique to
the problem, and if you have a homegrown access system…
I am not sure if this is an RT thing or if I should post it to MySQL &
PG lists instead, but I’ll start here.
I am currently about to trial RT in my office. Presently, to track
jobs we’re using a clunky old access DB. How hard will it be to
import this into my new RT database (either MySQL or PostGreSQL at
this stage…) ?
Has anyone done such a thing? I couldn’t find anythign that might be
useful anaywhere… Is it hard to make all the right fields end up
in the right place, etc?
TIA
Nemir
I upgraded us from Support Magic 3 to RT 2, using Access as the middle
step. First I imported all of the Support Magic data into identical
Access tables, and created ODBC links to the RT tables. I then figured
out the structure of RT and what fields and tables needed to be
populated (users, tickets, tranactions, keywords, attachments, etc).
Once I was confident in my testing that the tables were updating
correctly I wrote update queries in Access to copy the data from the SM
tables to the RT tables. I copied about 20,000 tickets and 100,000
transactions, and it worked great. As I recall the biggest problem I had
was not clobbering the RT transaction and attachment primary keys. I
don’t think I still have the queries or I would offer them up to you.
Access has been the bane of my existence for a long time, so I avoid it
as much as possible now…
