Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
readysetstop
Posting Yak Master
123 Posts |
 Posted - 2006-12-28 : 09:04:23
|
Having everyone and his brother with the ability to create their own DTS packages can be problematic.  It leads to a lack of documentation.What I need to do is find a way to associate the files that we load in the various DTS packages with their respective packages and databases that they are loaded to. What I'd like to end up with is a table that lists the database name, load package, and file loaded. What table it gets loaded to would be nice, but isn't really necessary at this point since the file names tend to mirror the tables, and that info wouldn't be critical unless the load failed anyway.If all else fails, I can certainly go package by package and check all the steps. For about 250-some packages.  Fun.Not looking for a finished script, unless someone already has one. A nudge in the right direction would be good. I was originally thinking I could get this info from the MSDB database somehow, but it looks like it stores most object names as binary identifiers, and those are pretty inconsistent. (I was able to find three separate binary IDs for one text file, all for the same DTS package, and no idea how they related to the package.)Any and all input is appreciated. Thanks!-d. |
|
|
|
|
|
Auditing DTS package input files. Ideas?