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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DTS Error - Too Many Columns;non-whitespace characters

Status
Not open for further replies.

smedvid

MIS
May 28, 1999
1,228
US
Ok, I have a strange "mystery" for SQL Server Experts:

I have a large text file delimeted by ~. The file has 85 cols and approximately 3.2 million rows. Text file is around 1.6 GB. I have a DTS in production that can import this file and the DTS in my Dev/Test area will not. I get the "Too Many Columns;non-whitespace characters" error in Test/Dev.

I have found that SQL Server Versions are slightly different in Prod and Dev:
----------------------
SELECT @@VERSION -- PROD
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0
(Build 2195: Service Pack 4)

SELECT @@VERSION -- DEV/TEST
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Personal Edition on Windows NT 5.0
(Build 2195: Service Pack 3)
----------------------

Any other clues are appreciated! I worked on this issue over 20 hours without any conclusions thus far.

I copied the DTS from PROD to see if I had something wrong in DEV. I also check hardware in Dev: plenty of free disk space and 1GB of RAM. Could I have a corrupt DB or something? Ugh!

Thanks in Advance,

Steve Medvid
"IT Consultant & Web Master"

Chester County, PA Residents
Please Show Your Support...
 
I was hoping to avoid the SPs but, I suspected that was one thing that I needed to try in order to mimic the Production SP4 environment with Dev SP3x. Any otehr ideas are welcome...

Steve Medvid
"IT Consultant & Web Master"

Chester County, PA Residents
Please Show Your Support...
 
Another simpler option is to create an ODBC Text DSN for the file.


Dr. Sql
Good Luck.
 
Funny u mentioned that - I have been try that this morning.... it is stull running... thanks,

Steve Medvid
"IT Consultant & Web Master"

Chester County, PA Residents
Please Show Your Support...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top