June 21, 2011 at 2:33 pm
We're in the process of killing this sql 2k server (can't wait!) I'm not very familiar with the DTS workings of the pre 2005. I'm trying to update a DTS package that does the following:
T SQL Statement - Trucates a table, executes a xp_cmd command to create an excel file based on a template excel file (created by copying a template file to a new location) The template file is just a few column names.
Piped into:
Microsoft data link to database
Piped into:
Another Microsoft data link (copy if the previous)
Piped into:
T SQL statement - Select top10 * from table (the same table truncated in the initial t sql statement.
Piped into:
Another Microsoft data link (copy of the copy....)
Piped into:
Microsoft excel ouput file (the file created in the initial t sql statement)
Piped into:
T SQL Statement - Serious of xp_cmd commands to archive this output file.
My question is, How is the truncated table being repopulated? How is the excel file being written?
I don't understand these UDL files that are being referenced in the Microsoft Data Link steps. If I try to open the file outside of EM, it goes straight to the properties window from the Windows Data Link Steps. How is the table being specified? How are the rows being specified?
June 22, 2011 at 10:37 am
The Data Links are merely the containers for database connection information, as you've seen when opening the .udl files.
I think, if you double-click on the gray arrow between two Data Link connections or between a Data Link connection and Excel, you'll find that it's a Transform Data task, not just a workflow connector. The Transform Data task is the primary task in DTS for actually moving data and that's how the data to be move is specified.
Greg
June 23, 2011 at 8:01 am
thank you!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply