November 6, 2009 at 1:26 pm
Another option is to look at the file as text. It is not too hard to parse out the SQL tranactions.
The connection information is at the top and the package flow down from there. As far as the file connection there usually needs to be a file there for the package to pass validation prior to executing. Maybe there is a SQL job or another package that creates the file and removes it?
November 6, 2009 at 1:27 pm
Karen Roslund (11/6/2009)
The sqlSourceType is a fileConnection and the FileConnection is AllowedtoFailPrologueSqland i cannot find that file from the server where the ssis package is located...
If the SourceType is a file connection, then is would be listed in the Connection Managers, is it not there?
I remember you have listed the Control flow tasks, there you mentioned AllowedtoFailPrologueSql once, is this Fileconnection property pointing to that?
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 6, 2009 at 1:29 pm
In my connection manager i have the file name but if i try to look for those files that directory doesnt exist at all...
Since these packages were created by some consultants outside the co... I think those files may reside on their server...
November 6, 2009 at 1:38 pm
Those Files and Directories must be existing on the Server where SSIS Packages are deployed, check and you should find them.
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 6, 2009 at 1:46 pm
--Oops, please ignore!
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply