HomeForum
Welcome, Guest

Attempting to load with visual importer.
(1 viewing) (1) Guest
Data Warehousing and Data integration
  • Page:
  • 1

TOPIC: Attempting to load with visual importer.

Attempting to load with visual importer. 10 months ago #3259

  • Ted
  • OFFLINE
  • Fresh Boarder
  • Posts: 5
  • Karma: 0
Attempting to load with visual importer.
Load fails with 1/o error 103.
Suspect problem is load of very large text field (over 54Kb). Target is sqlserver, d/b is 2005.
Field was ntext, changed to nvarchar(max).
Still fails, in map field type still shows as ntext, not nvarchar.
Any suggestions?

Ted

Re: Attempting to load with visual importer. 10 months ago #3260

  • admin
  • OFFLINE
  • Moderator
  • Posts: 2183
  • Karma: 12
i/o error 103 is file handle error

Most likely it has nothing to do with loading the data.

Have you got enough user rights?
Do you have any files open.
what is your source database?
Can you email us your log file please

Mike

Re: Attempting to load with visual importer. 10 months ago #3261

  • Ted
  • OFFLINE
  • Fresh Boarder
  • Posts: 5
  • Karma: 0
Hi Mike,

As I continue to work to load this data I have discovered that the problem appears to be related to the size of the memo field we are trying to load.
Most recent failure is: Access violation at address 00407090 in module 'VImp.exe'.
Read of address 656B614C. While the program appears to terminate it remains in memory and keeps the foxpro table locked. Need to kill it from taskmanager.

The source is a Visual Foxpro 9 database. The table in question contains 498,498 records. I have sorted the table in memofield size order for the load attempt. Sizes of the field arange from 1 char to 922,361 characters. Field is a police report, simple text.

It appears that the load fails after about 498,201 records (last attempt) with a record (memo field) size of 71,099 for the last successful record. The fail record appears to be 71,107 in size, and all subsequent records are
larger.

Note that attempting to start visualimporter with the large records first simply hangs and must be killed from task manager.

Target database is SQLServer2005, field in question is defined as text.
Is there some size limit that I should be aware of which limits the size of the field that can be processed?

Thanks for you help,

Ted
  • Page:
  • 1
Time to create page: 0.16 seconds

Testimonials

Within an hour we were able  to populate fact and dimension tables in our datawarehouse using Advanced ETL Processor

P. Jonson

User Login

You only need to log in or register to use our support forum



Our customers

BP

BBC

HSBC


Databases we work with

Go to top