Viewing 15 posts - 13,066 through 13,080 (of 13,876 total)
As you have things up and working, you've probably lost the urge to change how it operates now (I know I would!).
And given that you have so few source records,...
November 24, 2008 at 1:36 pm
The script task, as you have discovered, is just a place where you write VB.NET code and was, I believe, included to cover those situations where the other SSIS components...
November 24, 2008 at 1:19 pm
Just use a lookup from your source 'Item' data to retrieve the ID of the newly created Item and then use that to populate your ItemComments. No need for the...
November 23, 2008 at 3:19 pm
If it's numeric, cast to integer, otherwise leave as is:
declare @value varchar(10)
Set @Value = '0000006708'
if IsNumeric(@value) = 1
select cast(@value as integer)
else
select @value
Phil
November 19, 2008 at 8:13 pm
Not hard with a script component. Here's a snippet - assumes variables declared and strFilepath, strFilename have been set:
'Connect to the CSV file and...
November 19, 2008 at 7:19 pm
What do you want to do in those cases where the date is invalid? Error? Import the record with a null date?
November 18, 2008 at 6:16 pm
You want to execute a query that returns a resultset and iterate around that? Can you provide more detail about what you are trying to achieve?
November 18, 2008 at 3:16 pm
Excellent! Good to hear.
Phil
November 18, 2008 at 5:11 am
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
Viewing 15 posts - 13,066 through 13,080 (of 13,876 total)