We have a customer whos database I recently upgraded from
SQL 6.5 to 7.0 WITH UPGRADE WIZZARD. The database was EMPTY
when doing so. I haven't done anything more with the database,
like finetuning indexes.
One essential part of the application wich uses the database is
reading BIG textfiles into tables. In a week now we have read
in about 150 4 MEG textfiles into the database. (This isn't common,
there will only be one file a week in the future)
HOWEVER: I turns out that SQL 7.0 needs 3 - 4 times more time to read
texfiles and update tables.
I checked the statstics info with STAT_DATE (or something like that)
and it looks like the statistics are updated since the dates
are recent. Therefore I haven't ran the UPDATE STATISTICS yet.
Unfortunately there are no stored procedures for handling the update,
every row is handled in VB and every row is added and updated from
VB with RDO. I think the database is opened and closed frequently
under the reading / updating sessions. But why do I have the
What could be wrong?