Hi All,
I'm new to dts stuff. I've designed a dts package to create renewed
licences. It loops through a number of files, imports the data into a
temporary table and does a lot of processing on this table to create
new Licence table records, mark licences as renewed and add extra table
entries for the new licences created. There's quite a lot of
processing going on once the data is imported. Is the dts package the
best place for this to happen?
Thanks,
R.

Oh the theology of DTS... DTS is the DBA's window into a developer's
world - filled with wizards and gadgets a plenty - it can do anything;
so now the irony is that now that you have done it you ask "should I
have?"

Just as with using any wizards - if it is a one off, now its done so
walk away and never revisit because nothing will change - then you are
safe - walk away.

If you expect remodeling, enhanced requirements, interoperability with
other systems, or scalability - then best spend the time now to
architect a simpler DTS portion - move the complex routines to either
stored procedures or into a middle tier such as Java/.Net which are
readily serviced from a application server.

DTS helps bridge the gap between databases and systems using FTP /
OLEDB and many other choices - use it for where is shines best!


tagline: avoid flame