![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I am interested in auditing dts packages via 2 scenarios: 1. Ensure the dts package doesn't change from one day to another and... 2. Compare a dts package from one dB to another. Can someone provide any suggestions? For #1 - i would assume i can query the sysdtspackages table to ensure no new row was created between yesterday and today and that would show consistenty. But for #2 - how would i be able to compare the details of the dts package. Seems like the sysdtspackages table contains the detail only in binary format? I need to ensure that any task/property in one dts is the same as another on a different db server. So i need a way to compare the specific dts tasks in a format that allows me to see any differences. Any suggestions are appreciated. Thanks. |
#3
| |||
| |||
|
|
#1 - True enough (but as you know that really only shows whether the package was saved, not changed). |
|
#2 - I've been wondering about this myself. Maybe you can compare the two binary files, but of course that won't tell you what, specifically, was changed. One way that comes to mind is to "thumb through" the steps and tasks of a given DTS package and compare that to a table of expected steps and tasks. That would also allow you to compare a DTS package on one server to that on another. This could be done from a stored procedure (using the sp_OA* procedures) or from a vbScript or from another DTS package designed for auditing. Of course, this would all be a heck of a lot simpler if there were sysDTSsteps and sysDTStasks tables. The thumb through approach is certainly viable, and the old ScriptPkg |
#4
| |||
| |||
|
|
-----Original Message----- #1 - True enough (but as you know that really only shows whether the package was saved, not changed). #2 - I've been wondering about this myself. Maybe you can compare the two binary files, but of course that won't tell you what, specifically, was changed. One way that comes to mind is to "thumb through" the steps and tasks of a given DTS package and compare that to a table of expected steps and tasks. That would also allow you to compare a DTS package on one server to that on another. This could be done from a stored procedure (using the sp_OA* procedures) or from a vbScript or from another DTS package designed for auditing. Of course, this would all be a heck of a lot simpler if there were sysDTSsteps and sysDTStasks tables. "Rich" <rrabin (AT) z-tel (DOT) com> wrote in message news:049f01c37151$bf5f0130$a001280a (AT) phx (DOT) gbl... I am interested in auditing dts packages via 2 scenarios: 1. Ensure the dts package doesn't change from one day to another and... 2. Compare a dts package from one dB to another. Can someone provide any suggestions? For #1 - i would assume i can query the sysdtspackages table to ensure no new row was created between yesterday and today and that would show consistenty. But for #2 - how would i be able to compare the details of the dts package. Seems like the sysdtspackages table contains the detail only in binary format? I need to ensure that any task/property in one dts is the same as another on a different db server. So i need a way to compare the specific dts tasks in a format that allows me to see any differences. Any suggestions are appreciated. Thanks. . |
![]() |
| Thread Tools | |
| Display Modes | |
| |