Migrating large data sets into RTC
I am working with a customer that has a large amount of data to migrate from another tool into RTC/RQM. Much of the data can be exported into String type data, into csv files. However a large portion of the data is represented as CLOB (attachments, comments, and other multi-line fields). I am thinking of loading the "easy" data in first. And then using data base tools to load in the large attachment data and other CLOB data, then adjusting the links table to point to the relevant entries. This is a strategy that we have used many times with ClearQuest. With RTC, I've yet to do this, so I am not as familiar with the table structure relating the attachments, links and other internal representation. Any comments on this approach? I am also interested in any performance related data you may have achieved in migrating or loading large data sets into RTC's work item module.
|
4 answers
Ralph Schoon (63.4k●3●36●46)
| answered Jun 28 '11, 4:24 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER I am working with a customer that has a large amount of data to migrate from another tool into RTC/RQM. Much of the data can be exported into String type data, into csv files. However a large portion of the data is represented as CLOB (attachments, comments, and other multi-line fields). I am thinking of loading the "easy" data in first. And then using data base tools to load in the large attachment data and other CLOB data, then adjusting the links table to point to the relevant entries. This is a strategy that we have used many times with ClearQuest. With RTC, I've yet to do this, so I am not as familiar with the table structure relating the attachments, links and other internal representation. Any comments on this approach? I am also interested in any performance related data you may have achieved in migrating or loading large data sets into RTC's work item module. Hi Dave, I have always tried to avoid manipulating the database directly. I have created an importer myself that was able to import work item data and upgrade existing work items in the past, when the CSV import was not available. I used the plain java API for that. Dependent on the format of the input file(s) such a solution would also be able to upload multi line descriptions. It could also be used in conjunction to the existing CSV import. It could run multiple passes for efficiency and to create relationships between artifacts in a pass after the elements have been imported. If the exported attachments and the file name data for these attachments where available in the input data it would be possible to upload that data. There might be example implementations for this. I have example code for most of the pieces. |
|
The only time I go to the data base level is for speed when all other paths are not practical. It sounds like you created something similar to the CQ importer. I would be interested in trying your pieces out.
|
|
Use the utility our group has created to migrate work items.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.