January 11, 2010 at 1:40 pm
Hi,
I have SSIS, on Windows 2003 and SQL 2005, which import rows from pipe delimited csv file. Although there is only one row in csv file, however, the import job kept running. It seems to me that SSIS (and procedures that process the data in staging table) sees there are a lot of rows (or maybe endless) in file. Is there a good way to detect special characters in SSIS or procedure? Thanks.
Chris
January 11, 2010 at 4:15 pm
This does not sound like a case of a special character. It sounds like the package is hung up on a step.
Can you describe the control flow tasks prior to the data flow in question and also detail the tasks inside of the data flow? What are you trying to do with the data? Are you using precedence constraints that contain expressions, or script tasks?
January 12, 2010 at 9:32 am
John,
Thanks for the help.
SSIS move files from 5 application to SQL servers, check file name, header, load into staging and start processing rows (creating rows few different base table). You were right the package hung due to INSERT NULL error. There is a row:
SELECT @RoleGenerateID = SCOPE_IDENTITY()
right after INSERT. That might be the reason identity column jump from 5 to 6 digits in one table. But what surprised me was that I added a DELETE way before the processing:
DELETE dbo.stg_RolePlayer
WHERE ISNUMERIC(RoleID) <> 1
right after staging was populated. The DELETE resolve the issue.
In any case, thanks again/
Chris
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply