Hello Kevin,
> Does anyone have any details of whether MapInfo has any
> technical/performance issues with working with large tables. We have a
> project at the moment where we are seeing a steep performance dropoff when
> inserting records into a tables. The table with the worst performance at the
> mo has about 300k rows in it (all mappable objects).
I've not noticed any significant drop-off in performance with large tables. I
regularly build the
gazetteer from Global Insight (>338,000 records) and it doesn't take long. Do you have
any
indexes (please, nobody tell me it should be "indices"!) active? If so, this is almost
certainly the
problem. MapInfo does not have particularly good index updates. In fact, sometime I
think it builds
the whole index again. The solution is to suspend/delete the indexes and rebuild them
after you're
done inserting. Unfortunately, for some multi-user apps, this isn't always practical.
Might be worth playing with turning off the transaction management and undo features
too:
set table <TableName> fastedit on undo off
Regards,
Warren Vick
Europa Technologies Ltd, U.K.
http://www.europa-tech.com
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
