October 29, 2001 at 8:51 am
Excuting a Stored Procedure from a DTS package is very simple while working with a "Execute SQL Task". I would be very glad if anyone could tell me a good way of using Stored Procedures in transformations tasks such as "Data Driven" or "Transform Data Task".
October 29, 2001 at 10:36 am
So far I haven't found one (I'd like to do this as well), but I'll keep looking. Pls post if you find one and I will do the same.
Steve Jones
October 29, 2001 at 11:39 am
Actually it isn't impossible to perform this action. But I only obtained success when the destination Database has a table composed of fields that could represent the parameters of the Stored Procedure. In my opinion, keeping an empty table like that is not a good practice.
November 1, 2001 at 7:01 am
If the transformation is an ActiveX script, you could use the execute method of the command object in ADO. Alternatively, the Task object in the DTS heirachy - accessible through Globalvariables.Parent.Tasks("taskname") - does have an Execute method, although getting the correct arguments to send is something I haven't figured out yet.
Paul Ibison PhD, MCSD
email: Paul.Ibison@btinternet.com
Paul Ibison
Paul.Ibison@replicationanswers.com
November 1, 2001 at 10:04 am
I discovered if you uncheck he "7.0 forma" button on the options tab, the source fields are accessable in the transformations tab.
Steve Jones
November 1, 2001 at 10:41 am
Hi Steve,
I suppose there's no relation between the 7.0 format on the Options tab and the accessibility of the source fields on the Transformations tab. 7.0 format is the text file format generated with a log of the Data Driven execution. I'm trying to follow the PaulIbison's tip but I still can't execute a task of package from the script of my Data Driven.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply