Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Seek Failed Error

Status
Not open for further replies.

Kelin

Technical User
Dec 12, 2002
11
US
During the importation of a large number of records(1,495,000) on SQL Server 2000 to a table from a flat delimited file, a error is encountered when the import approaches 1,400,000. Error: Seek failed on an unnamed file. If we delete the top or bottom 400,000 records, the import works fine. This leads me to believe there is a possible memory limitation in MSSQL. Is this an accurate assumption? Any ideas on what could cause this? We thought it might be corrupt data but since we can solve the issue by deleting the top or bottom 400,000 records, it appears to be a size/memory issue.
 
Did you resolve this issue? If not, can you provide us w/ the exact error message(s) and error numbers.

Is it feasible to split your file into two files and run your procedure? Just a thought!

Thanks

J. Kusch
 
This is a shot in the dark, but run sp_dboption '[database name here]','select into/bulkcopy' in Query Analyizer. If this is set to OFF, then DTS logs the insertion of all 1.4 million rows and you may be hitting a size wall. Set the db option to ON by runnning sp_dboption '[database name here]','select into/bulkcopy','ON' and DTS will not log and will be tons faster.

Hope this helps.
SQLRickster
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top