Using the DTS GUI Interface (DTS Designer) is very easy. Depending on the
complexity of your DTS package you may want to document what to do to
implement these future changes, instead of trying to understand how the
package works after you have not seen it for weeks or months.
Ben Nevarez, MCDBA, OCP
Database Administrator
[quoted text, click to view] "Robert Bravery" wrote:
> Thanks Ben,
> Next question:
> How easy would it be to update the dts package on a clients machine when and
> if structure and protocol changes.
> Thanks
> Robert
>
> "Ben Nevarez" <bnevarez@sjm.com> wrote in message
> news:256513B7-AABF-4276-9E7F-2343D256C30B@microsoft.com...
> >
> > DTS is the right tool for this task.
> >
> > Although I would not be surprised if a very experienced C# developer with
> > basic DTS knowledge can write this application a lot faster than writing
> the
> > DTS package.
> >
> > Ben Nevarez, MCDBA, OCP
> > Database Administrator
> >
> >
> > "Robert Bravery" wrote:
> >
> > > HI all,
> > >
> > > Which is better, to use DTS for CSV type file imports or to write your
> own
> > > import app.
> > > Considering the following that it is most likely that the structure of
> the
> > > import file will change a few times within the next year, and that this
> is
> > > not inhouse but for an outside client, and that they would most probably
> be
> > > using SQLXpress
> > >
> > > Value your thoughts
> > >
> > > Thanks
> > > Robert
> > >
> > >
> > >
>
>