Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Automating DTS Execution


Automating DTS Execution

Author
Message
augustin Carnu-215787
augustin Carnu-215787
Grasshopper
Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)

Group: General Forum Members
Points: 16 Visits: 1
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/gcarnu/automatingdtsexecution.asp


Cheers,


Augustin Carnu


kristien van dijck
kristien van dijck
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 1

good article.

Thanks for the information supplied.


Mark Storey-Smith
Mark Storey-Smith
Valued Member
Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)

Group: General Forum Members
Points: 58 Visits: 305

"If you were to replace the Child package for some reason, like saving it after making changes, this would create a completely new VersionID, with a new time stamp and a new ProgramID! And this would break the linkage between packages, as the VersionID is pointing to an old VersionID with the same name. The PackageID {543E….184} in the background of Figure 2 is obsolete, and the execution will fail!"

This is not strictly true. When choosing the package for an Execute Package Task, point to the package name instead of a specific version and the task will always use the latest version. You can make changes to the child package (which will change the versionId) but the packageId will not change so the Execute Package Task will not need to be updated.


Philippe Cand
Philippe Cand
SSC Journeyman
SSC Journeyman (84 reputation)SSC Journeyman (84 reputation)SSC Journeyman (84 reputation)SSC Journeyman (84 reputation)SSC Journeyman (84 reputation)SSC Journeyman (84 reputation)SSC Journeyman (84 reputation)SSC Journeyman (84 reputation)

Group: General Forum Members
Points: 84 Visits: 294

Hi,

I too find quite unstable to use the run package task within a DTS and use the Jobs instead to chain the DTS.

For portability reasons, I do not let the standard command string in the job, I replace it with the command line generated by DTSRUNUI so the job refers to the package name rather than the ID.

This makes easier the task to move jobs to another server using a script.

I also use a network alias rather than either Local or Machine name.

Example, in the SQL Server Client Network Utility, i create an alias i.e "Datamart" that point to the machine I want. i have the same alias in all machines. I use this alias in all packages, jobs and connections so they will allways resolve to the machine I want. For servers, it is the local machine, for dev boxes, I manipulate the alias so my dev instance will take data from the server I want.

Last but not least, I use DTS Backup 2000 to move DTS packages from server to server and i use the server's DNS name in the OLAP Cubes connections or Query connections so if I change Production Server, I simply swap the DNS entries and all user's queries now repoint to another machine without the user's knowledge.

Take care, Philippe



BI Guy
Calvin Lawson
Calvin Lawson
Right there with Babe
Right there with Babe (738 reputation)Right there with Babe (738 reputation)Right there with Babe (738 reputation)Right there with Babe (738 reputation)Right there with Babe (738 reputation)Right there with Babe (738 reputation)Right there with Babe (738 reputation)Right there with Babe (738 reputation)

Group: General Forum Members
Points: 738 Visits: 102

"The comment about registering the server as "Local" to ensure portability tweaks my interest. I'm wondering how you register a named instance as "Local"..."

By default a named instance can be referred to as " (local) ", if only one named instance of SQL Server exists on the box.

As for the author, it seems like this is a work-around for not clicking directly on the package name when choosing the child package. Maybe he didn't know you could do that?

On a similar note...

By default the "DTSRUNUI" generates something like:

DTSRun /S "(local)" /N "zTEST-DTSRun" /G "{32E787CD-4764-4D7A-820C-43888AE1F87C}" /A "Body":"8"="TestBody" /A "Subject":"8"="TESTSubject" /W "0" /E

This has both Name and PackageID specified. Name is portable, but PackageID is not. Removing PackageID from the command string fixes this problem, and does not affect the exection of the package.



Signature is NULL
Alex C-219694
Alex C-219694
Forum Newbie
Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: General Forum Members
Points: 5 Visits: 1
great content. figures helped a lot. overall a very helpful article.
gabriela-219983
gabriela-219983
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 1

Very original article on an interesting topic, and also very well written.


mmmmmmmmmmmmm
mmmmmmmmmmmmm
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 1
Very good article, concise information and excellent presentation.
augustin Carnu-215787
augustin Carnu-215787
Grasshopper
Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)

Group: General Forum Members
Points: 16 Visits: 1

Our requirements were very clear:
- Make our DTS workflows available for CD distribution to new and existing clients
This eliminates the ActiveX variant suggested by another reviewer; we cannot ssume that ClientX or ClientY, Z, etc - will allow us to install and run our controls. It's the reality out there...
- Bring them in the DTS editor for running, no DTSRUN command line running.
- Allow modifications by the Cleint using the visual interface
- Make sure that any modifications at the client will not break package chain execution, as long as there is only one version present.
Cheers,

Gus




Cheers,


Augustin Carnu


augustin Carnu-215787
augustin Carnu-215787
Grasshopper
Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)

Group: General Forum Members
Points: 16 Visits: 1

The name only doesn't work....

Our requirements were very clear:
- Make our DTS workflows available for CD distribution to new and existing clients
This eliminates the ActiveX variant suggested by another reviewer; we cannot ssume that ClientX or ClientY, Z, etc - will allow us to install and run our controls. It's the reality out there...
- Bring them in the DTS editor for running, no DTSRUN command line running.
- Allow modifications by the Cleint using the visual interface
- Make sure that any modifications at the client will not break package chain execution, as long as there is only one version present.
Cheers,

Gus




Cheers,


Augustin Carnu


Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search