I am importing a textfile using TransferText. There are about 50000 records in the textfile (6mb in size). When the Database is on the local harddrive the import takes about 5-10 secs.
I had to make the DB available to other people and put it on a LAN drive. When I now run the TransferText the import takes a lot longer. I gave up waiting after 20mins so don't actually have a time how long it takes. I reduced the text file to 14kb just to prove there were no unexpected errors (there were none). I could see the NetWork activity was at about 10-15% while the TransferText was running.
The text file that is imported usually resides in c:\temp but moving it to the lan location made no difference.
The Lan connection is a 100Mbps full duplex and is not the problem. It takes 2 secs to copy the DB to/from the lan.
Has anyone got any ideas why it would take so much longer. When running queries on the DB while its on the LAN the response is somewhat slower, compared to being on the local harddrive (instead of 1 sec it takes 2 secs maybe) and that's acceptable and expected.
I had to make the DB available to other people and put it on a LAN drive. When I now run the TransferText the import takes a lot longer. I gave up waiting after 20mins so don't actually have a time how long it takes. I reduced the text file to 14kb just to prove there were no unexpected errors (there were none). I could see the NetWork activity was at about 10-15% while the TransferText was running.
The text file that is imported usually resides in c:\temp but moving it to the lan location made no difference.
The Lan connection is a 100Mbps full duplex and is not the problem. It takes 2 secs to copy the DB to/from the lan.
Has anyone got any ideas why it would take so much longer. When running queries on the DB while its on the LAN the response is somewhat slower, compared to being on the local harddrive (instead of 1 sec it takes 2 secs maybe) and that's acceptable and expected.
