LOL In my mind - there would be a operator map tool here - I don't think the tool could be self aware enough to figure out every possible combination of everything.
It could certainly "guess" 80% correctly and be corrected on the remaining 20% on suggesting maps. I see this with data going from MV to SQL - sometimes the dictionaries are just wrong... it's easier to adjust using the map... (in particular if they're not your dictionaries to adjust) I would imagine an adjustment could be made to the maps to increase MV performance - just like you would in SQL when porting MV data there. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Robert Houben Sent: Friday, December 24, 2010 1:41 AM To: U2 Users List Subject: Re: [U2] Migration Oh, one more point. What if your SQL environment had NOT defined a primary key for APPOINTMENTS, but had multiple indexes, one of which happened to have CUSTOMERNO, APPTDATE, APPTTIME and APPTTYPE. How would you figure out what to use as the item-id of the PICK file? What if you had a SQL table that actually did not have a set of fields that guaranteed a unique value? Then you have NOTHING to create an item-id from! I have to stop this, it will consume me! :o But the list goes on. Oh the humanity! _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
