August 30, 2005 at 11:33 pm
Hi, I have a DTS job, that I call from a batch file, to import csv files.
The job works fine except that all of the data pumps stop at 773 rows!
Neither "773", or any other row limit, appears in the files, the batch job, the global variables or the DTS source.
Anyone have an idea as to what is happening here?
Code for one of the DTS transforms is attached (they are all identical except for the source columns and some minor logic).
Thanks,
-- MikeR
'**********************************************************************
' Visual Basic Transformation Script
'**********************************************************************
'**** This transform is for the a generic, modern, PSG file Type. ****
Function Main()
'---- Ignore bad rows and the case when the temperature=0 (always signals a fatal error as a side-effect of the test execution). ---
If ((DTSSource ("Col008") = "0") OR (DTSSource ("Col011") = "") OR IsNull (DTSSource ("Col011")) OR NOT IsNumeric (DTSSource ("Col011"))) Then
Main = DTSTransformStat_SkipInsert
else
DTSDestination ("sSerialNum") = Trim (DTSSource ("Col003"))
DTSDestination ("fParamValue") = Trim (DTSSource ("Col011"))
DTSDestination ("iPortNum") = 0
DTSDestination ("sPartNumber") = Trim (DTSSource ("Col001"))
DTSDestination ("sPC_Name") = "SET FROM FILE PATH!!"
DTSDestination ("sUnits") = "count"
'--- Convert the pass string into a bit. ---
'
If (LCase (Trim (DTSSource ("Col004"))) = "pass") Then
DTSDestination ("bPass") = 1
else
DTSDestination ("bPass") = 0
End if
'--- Convert the separate date and time into the DT column. ---
'
DTSDestination ("zTestTime") = DateValue (Trim (DTSSource ("Col005"))) + TimeValue (Trim (DTSSource ("Col006")))
'--- Special Destination fields. ---
'
DTSDestination ("sSourceFilePath") = DTSGlobalVariables("sSrcFilePath").Value
DTSDestination ("sSourceFileName") = DTSGlobalVariables("dtsFileName").Value
DTSDestination ("sParamName") = "TCC_PowerSenseCalChanB"
Main = DTSTransformStat_OK
End if
End Function
August 31, 2005 at 12:32 am
Never mind.
Finally discovered that SQL server had somehow corrupted a global variable adjustment in the package.
Fixed this and job again works correctly.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply