Viewing 15 posts - 13,036 through 13,050 (of 13,838 total)
Now I see what you're asking.
Well - you could create pack3.dtsx and in it create two linked 'Execute Package' tasks which execute Pack1 and then Pack2.
Or ... you could go...
November 18, 2008 at 4:54 am
I think people misunderstood your first post a little - you suggested that there could be varying numbers of fields on each record. To accommodate that scenario, scripting would be...
November 17, 2008 at 4:03 pm
SSIS will eat that up, no problem - that is standard CSV format. The fact that many of the source fields are NULL just needs to be accommodated as part...
November 17, 2008 at 3:30 pm
Michael gave you the answer. Change your destination component to be SQL Server, not OLEDB, and the option is there.
Phil
November 17, 2008 at 3:09 pm
If you do not know what created the DBF files, try using the built-in DBase driver.
If that does not work, try using FoxPro. As Greg said, you might have to...
November 17, 2008 at 3:00 pm
Set DelayValidation = True on the bit that does the import.
Surely your error is 'Source Not Found' rather than 'Destination Not Found'?
Phil
November 17, 2008 at 1:14 pm
Yuk - so how do you know what the data is in each field? Or is it just that there may be some missing fields at the end of the...
November 15, 2008 at 7:40 pm
CSV files are, by nature, not fixed length. Do you mean CSV files which have varying numbers of records on each line?
Phil
November 15, 2008 at 3:21 pm
Jack's idea is a good one and can, of course, be accomplished in a single package using an initial script task to check the number of columns with a conditional...
November 14, 2008 at 8:16 pm
Sounds like the SQL Agent service may be running with credentials which do not allow it to access the file. Is it on a network folder somewhere?
November 14, 2008 at 8:11 pm
No - this error was driving me so mental with irritation that I had to give up before I snapped!
I now use traditional copy/paste methods to get the job done...
November 13, 2008 at 12:50 am
Create a Boolean variable IsWeds.
Create a script task containing some code like this.
Public Sub Main()
Try
Dts.Variables("IsWeds").Value = False
...
November 10, 2008 at 3:22 pm
Explicit selection of only those columns which are required is surely the way to go here? Select * from xxx will often throw things out when the underlying xxx schema...
November 2, 2008 at 8:22 pm
A reinstall of VS2005 and .NET Framework 2 has not fixed it. Bizarre.
October 30, 2008 at 11:07 pm
Steve, don't want to be picky, but as it's the title of your article ... I think the word you're looking for is 'savvy' 🙂
PP
November 26, 2007 at 9:53 pm
Viewing 15 posts - 13,036 through 13,050 (of 13,838 total)