|
|
You're in the
sql server dts
group:DTS and version control software
sql server dts:
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
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%20Server\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 [quoted text, click to view] "Richard G" <a@a.com> wrote in message news:OZkd5xIfFHA.1044@tk2msftngp13.phx.gbl... > Is there no way to show the columns associated with the target table name? > > "Narayana Vyas Kondreddi" <answer_me@hotmail.com> wrote in message > news:OJKXt%23HfFHA.3656@TK2MSFTNGP09.phx.gbl... >> 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 in message >> news:uTG3LOHfFHA.1416@TK2MSFTNGP09.phx.gbl... >> 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?
[quoted text, click to view] "Narayana Vyas Kondreddi" <answer_me@hotmail.com> wrote in message news:OJKXt%23HfFHA.3656@TK2MSFTNGP09.phx.gbl... > 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 in message > news:uTG3LOHfFHA.1416@TK2MSFTNGP09.phx.gbl... > 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/ [quoted text, click to view] "Richard G" <a@a.com> wrote in message I'm considering using DTS packages for certain database tasks. I have anews:uTG3LOHfFHA.1416@TK2MSFTNGP09.phx.gbl... 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
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. [quoted text, click to view] "Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message news:eEElqQNfFHA.272@TK2MSFTNGP15.phx.gbl... > 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%20Server\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 in message > news:OZkd5xIfFHA.1044@tk2msftngp13.phx.gbl... >> Is there no way to show the columns associated with the target table >> name? >> >> "Narayana Vyas Kondreddi" <answer_me@hotmail.com> wrote in message >> news:OJKXt%23HfFHA.3656@TK2MSFTNGP09.phx.gbl... >>> 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 in message >>> news:uTG3LOHfFHA.1416@TK2MSFTNGP09.phx.gbl... >>> 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 >>> >>> >>> >> >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |