unexpected info item

Question

Post reply

unexpected info item

dndaughtery

SSChampion

Points: 11290
More actions
April 13, 2009 at 7:46 am

#132810

Can anyone explain to me what the following error means:
Line 0 in format file "C:\Temp\LoadFilesForProcessing\CaseLevelData\Output Files\RawCases": unexpected info item.

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

Dave23 Hall of Fame Points: 3903 More actions · Answer 1

I think that it indicates that a data row doesn't match the structure that a format file is expecting.

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 2

dndaughtery (4/13/2009)
Can anyone explain to me what the following error means:
Line 0 in format file "C:\Temp\LoadFilesForProcessing\CaseLevelData\Output Files\RawCases": unexpected info item.

Could you post your format file so we may see it?

dndaughtery SSChampion Points: 11290 More actions · Answer 3

Well, thats my problem. I'm not sure how to create a format file from an SSIS Raw File. I was using the actual Raw file hoping that SSIS would generate it but that isn't the case.

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 4

When you are talking about a raw file, are you talking about a raw file also created by SSIS or are you talking about a flat file, like a CSV or fix-length file?

dndaughtery SSChampion Points: 11290 More actions · Answer 5

Raw file created by SSIS Raw File Destination object

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 6

dndaughtery (4/14/2009)
Raw file created by SSIS Raw File Destination object

With that, are you using a Raw File Source in the next package?

dndaughtery SSChampion Points: 11290 More actions · Answer 7

dndaughtery

SSChampion

Points: 11290

April 14, 2009 at 10:34 am

#977412

yes

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 8

I'm at a loss. When I was looking at Raw files, I didn't encounter this problem. I didn't go that route at the time anyway as I was pulling data from a SQL Server 2000 database, adn decided to direectly move the data to staging tables instead of raw files.

dndaughtery SSChampion Points: 11290 More actions · Answer 9

I'm actually getting the data in a flat file and then I run a package that converts it into one common schema we use and is placed in a raw file created by SSIS. I have another SSIS that loads from the formatted raw files into the database. That way if one of my data sources change i only need to make an update to that package and not every package for every datasource. Its ok though. I figured out that I could import it much quicker without using a Bulk Insert by doing the following:

set the packet size of the connection mgr to 32,767

uncheck the "Check Constraints" check box on the OLEDB Source

Drop indexes before inserting then be sure to re create them afterwards.

Just have the table lock checked, remove any null checks, constraint checks.

set the batch size to 100000 and commit size the same.