You cannot make the Trim String transformation the default.

Yes you can globally change then transformations but this will involve the
object model OR Disconnected Edit use and I think you want to stay away from
that.


--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know


"Adam Hauerwas" <Adam Hauerwas (AT) discussions (DOT) microsoft.com> wrote

Oracle "sqlplus" command-line execution, have a colsep of "|", and have
leading and trailing whitespace.
it to trim leading and trailing whitespace. Is there a way to make the trim
be the default, or a way to globally change all of my column transforms?
BTW, I am not using ActiveX script anywhere; I'm trying to stick to the GUI
for reproducibility and ease of use.
pumps -- but it seemed kludgy, and I thought I'd ask the group.

With text files I always import into a staging table first. I then perform
my manipulations from there.

Why can you not just set up the correct type of transformation when you
build the package?

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know


"Adam Hauerwas" <AdamHauerwas (AT) discussions (DOT) microsoft.com> wrote

all fields for a given table?

Maybe I could, and I'm just missing something. But it seems that to set up the transformations when I build the package I would need to a) delete all the standard Copy transformations and b) set up new transformations on a field-by-field basis for each of the incoming fields. If the fields in the text file were to ever change, I'd have to rebuild all the transformations for the additional field?

Excuse my inexperience, please -- I may be missing something basic here.

"Allan Mitchell" wrote:

OK

The trim String and Mid String can only have one Source attribute and
Destination attribute so yes you must

"Remove All" first then redo them. This will only need to be done once
though.

If the fields in the text file were ever to change then you would need to do
something about it anyway as DTS will not auto remap for you.

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know


"Adam Hauerwas" <AdamHauerwas (AT) discussions (DOT) microsoft.com> wrote

all the standard Copy transformations and b) set up new transformations on a
field-by-field basis for each of the incoming fields. If the fields in the
text file were to ever change, I'd have to rebuild all the transformations
for the additional field?

"Adam Hauerwas" <AdamHauerwas (AT) discussions (DOT) microsoft.com> wrote

all the standard Copy transformations and b) set up new transformations on a
field-by-field basis for each of the incoming fields. If the fields in the
text file were to ever change, I'd have to rebuild all the transformations
for the additional field?
If it's bothering you that much, maybe you should write your own
pre-formatter in VB or DotNet. You could write a reasonably simple tool
that would strip whitespace and maybe do some simple reformatting,
outputting a "cleaned" text file and simply use an Executable task to run it
as part of your package, then you run your transformation task on the
"cleaned" file. You could use this tool in other packages, too.