P4DTI issue job000374

TitleTeamTrack integration is slow because it reads too many change records
Assigned userGareth Rees
DescriptionThe P4DTI reads all records from the TS_CHANGES table since the last time it replicated. But some of those records are for changes to fields that aren't replicated. This wastes time. The P4DTI TeamTrack integration is now maintained and supported by TeamShare <http://www.teamshare.com/>.
AnalysisThe P4DTI could reduce the volume of data transferred by selecting only those records that match fields that are going to be replicated.
How foundcustomer
Evidence<http://info.ravenbrook.com/mail/2001/07/24/19-34-22/0.txt>, item 4.
Observed in1.1.3
Created byGareth Rees
Created on2001-07-24 22:28:25
Last modified byDavid Jones
Last modified on2003-08-19 13:55:18
History2001-07-24 GDR Created.
2003-05-19 NB TeamShare handover.
2003-08-19 DRJ Suspended due to teamshare handover


Change Effect Date User Description
35521 suspended 2002-11-14 13:44:46 Richard Brooksby Removing TeamTrack support from master sources.
Updating project index and FAQ to reflect new TeamTrack situation.