I'm considering using DTS packages for certain database tasks. I have a
policy that most if not all database activity must use database code (stored
procs, functions, etc). Currently, schema changes can be easily associated
with code by searching Visual Source Safe files for anything that's
associated with a particular table, etc. Stored procedures can be used to
get a result set for transformation objects, and those stored procedures can
be kept in Source Safe, but the target table is not stored that way in the
DTS code, that I know of. How can I use DTS packages so that the code can
be easily searched for tables, columns, and other objects can be easily
searched?

I've been using DTS for a long while, but only very basically, so any advice
will be appreciated.

Thanks,
Richard

You can open a DTS package and save it as a Visual Basic file. This should
contain the table name, and the VB file is searchable.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @ http://vyaskn.tripod.com/


"Richard G" <a@a.com> wrote

I'm considering using DTS packages for certain database tasks. I have a
policy that most if not all database activity must use database code (stored
procs, functions, etc). Currently, schema changes can be easily associated
with code by searching Visual Source Safe files for anything that's
associated with a particular table, etc. Stored procedures can be used to
get a result set for transformation objects, and those stored procedures can
be kept in Source Safe, but the target table is not stored that way in the
DTS code, that I know of. How can I use DTS packages so that the code can
be easily searched for tables, columns, and other objects can be easily
searched?

I've been using DTS for a long while, but only very basically, so any advice
will be appreciated.

Thanks,
Richard

Is there no way to show the columns associated with the target table name?

"Narayana Vyas Kondreddi" <answer_me (AT) hotmail (DOT) com> wrote

If you do not want to use Vyas' method then you can look at each DataPump
task and then look at each transformation object and get the
DestinationColumns property and then the column object

In BOL

mk:@MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\dtsprog.chm::/dtspothobj_7ovm.htm

--



Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


"Richard G" <a@a.com> wrote

Yes, my original plan was to store the VB code in source safe and use it to
search, but there doesn't appear to be a way to see the details of what is
being used by packages, such as destination columns, without writing some
sort of reverse engineering tool or opening the package in SQL Server and
looking at the properties of each task.

For now I'll let the developers continue writing C++ and stored procedures
to do these tasks. We have a very easy way to see and search all things
database that way.

Thanks for the input.

"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote