May 13, 2018 at 6:58 pm
Comments posted to this topic are about the item Auto assign Column Data Types for Flat file Source Import
May 14, 2018 at 3:11 am
As brilliant as simple. Thank you for sharing.
May 14, 2018 at 4:39 am
Simple, effective and well written. Good stuff.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
May 14, 2018 at 5:31 am
This is one of those great solutions that is both simple and innovative. You know you have something brilliant when you see it and say how did I not think of that.
May 14, 2018 at 6:14 am
Thank you, Daniel. Very well written and an excellent solution.
May 14, 2018 at 6:23 am
Great article and something I never thought about doing. I think you might have shaved about 20 minutes off my average time to create a source from scratch.
Thank you.
May 14, 2018 at 8:50 am
This is brilliant in its simplicity. No matter how much I learn about SSIS, it's always a pleasure to run across a gem like this. Thanks for sharing!
May 14, 2018 at 1:00 pm
Thank you for this tip. It will save me hours every month.
May 14, 2018 at 4:12 pm
Since SSIS packages are just XML files, you can also generate an XML definition for the source from the metadata of the destination table, and either dynamically or with just cut-and-paste in Notepad, you can create a data source pretty easily that way. I've done that before. Even automated it for a solution that had to import hundreds of dynamic file formats.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
June 26, 2019 at 2:06 am
Very effective. Well Explained.
Could you please help me with one step further, my requirement is as follows:
The columns of source table have datatype as CHAR (DT_STR), so the source table EXTERNAL column datatype value is DT_STR. The requirement is to read the data from the source table as Unicode characters, so we need to manually change the OUTPUT COLUMN datatype values for all the columns as DT_WSTR (Unicode). Just for information, the target tables have the dataype as DT_WSTR (Unicode). Please advise if there is any easy way to do this?
February 27, 2020 at 3:31 pm
Life Saver! Question: I create a master package with a variable value that determines source file names, path, target, etc. Is there a way that the initial dest to csv for auto datatype mapping can remain in the package, execute, and that the flow continues to the next piece? Meaning, can these two separate flows exist and execute consecutively or, do you have an easy way of calling another package?
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply