![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a DTS package that defines a Dynamic Properties Task, which in turn has 2 destination properties each of which define a data source generated by a SQL Query in an attempt to generate dynamic file names for 2 flat files based on the date/time. When I have the package open and execute the Dynamic Properties Task individually, followed by executing the entire package the output files are named as desired. When the package is executed by itself, and not preceeded by executing the dynamic Properties Task, one of the data files in not named correctly. It appears that both destination properties in the Dynamic Properties Task are not being executed. The Dynamic Properties Task "points" to a MS OLE DB provider based on a workflow success. the OLD DB provider in turn "feeds" two transform data tasks each of which results in a text file(destination) named by the Dynamic Properties Task. this is where one of the files in not named properly. How do I get both quries contained in the DP task to execute when the entire package is executed? |
#3
| |||
| |||
|
|
feil wrote: I have a DTS package that defines a Dynamic Properties Task, which in turn has 2 destination properties each of which define a data source generated by a SQL Query in an attempt to generate dynamic file names for 2 flat files based on the date/time. When I have the package open and execute the Dynamic Properties Task individually, followed by executing the entire package the output files are named as desired. When the package is executed by itself, and not preceeded by executing the dynamic Properties Task, one of the data files in not named correctly. It appears that both destination properties in the Dynamic Properties Task are not being executed. The Dynamic Properties Task "points" to a MS OLE DB provider based on a workflow success. the OLD DB provider in turn "feeds" two transform data tasks each of which results in a text file(destination) named by the Dynamic Properties Task. this is where one of the files in not named properly. How do I get both quries contained in the DP task to execute when the entire package is executed? Is the file connection being used elsewhere? You can have the situation when task A opens the connection, task B sets the filename, but this is does not take effect since the connection is open. Try setting close connection on completion for any tasks before the Dynamic Properties task, to ensure the connection is closed and ready to read the new information when re-opened. -- Darren http://www.sqldts.com http://www.sqlis.com |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
I have a DTS package that defines a Dynamic Properties Task, which in turn has 2 destination properties each of which define a data source generated by a SQL Query in an attempt to generate dynamic file names for 2 flat files based on the date/time. When I have the package open and execute the Dynamic Properties Task individually, followed by executing the entire package the output files are named as desired. When the package is executed by itself, and not preceeded by executing the dynamic Properties Task, one of the data files in not named correctly. It appears that both destination properties in the Dynamic Properties Task are not being executed. The Dynamic Properties Task "points" to a MS OLE DB provider based on a workflow success. the OLD DB provider in turn "feeds" two transform data tasks each of which results in a text file(destination) named by the Dynamic Properties Task. this is where one of the files in not named properly. How do I get both quries contained in the DP task to execute when the entire package is executed? |
![]() |
| Thread Tools | |
| Display Modes | |
| |