hi, we just decided to change over to a tab delimited format in a handful of dw files coming our way. the pkg was already set up to consume .csv's. my peer decided to send the files with a .tsv extension. i have to admit ive nebver heard of .tsv and already noticed even before going into the pkg that windows doesnt know without being told what to open the files with.
my gut from stuff i did years ago says to tell her to keep her .csv extension because windows and ssis are ok with .csv's using a delimeter different from comma.
im concerned about having to redo all the mappings etc.
does the community have a suggestion for path of least resistance when i go in to change the pkg? and if she can keep her tsv's.
the extension does NOT matter for SSIS - you give the filename whatever name+extension you wish.
as long as the format of the rows is what you defined everything will work as expected.
also the delimiter is whatever you defined - and this is regardless of it being a .csv or something else.
as for your windows not knowing what a TSV file is - you can tell it what it is and what default program to use.
but again there is no reason to change a existing process using .csv to something else so I would still go back to your peer and ask to revert back that change.
October 16, 2024 at 2:03 pm
thx frederico, thats good to know and i think a the answer. i think to avoid problems when someone tries to open a .csv that really isnt a csv by double clicking from windows, im probably going to try to talk her into a .txt extension. i'll post back here shortly. im going to poke around the internet a little .
October 16, 2024 at 2:19 pm
ok, tsv is a known file extension. who knew. i think now if i can consume a tsv in ssis (like frederico said) with no problems i'll ask her to go with tsv. the reasons are as follows...
i'll post back here.
October 16, 2024 at 2:55 pm
Frederico's message is spot on, as usual!
In my opinion, Excel should almost never be used to view *sv files, because as part of its parsing, it tends to display values differently from how they appear in the underlying file.
If you want to change the association between a file extension and the default application it opens with, that's a straightforward Windows config change.
There are plenty of better (but more niche, I admit) utilities for viewing *sv files in a readable format. I rarely need to do that, but when I do, I simply use VS Code, with the Rainbow CSV extension.
October 16, 2024 at 7:04 pm
i consumed the tsv files in ssis ok. of course i had to change the delimiter to tab (columns in the connector edit->and you see that delim). and i did run into some trunc issues on derived cols but convinced myself they werent a showstopper.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply