dbTalk Databases Forums  

Dynammic Properties for connection(s)

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss Dynammic Properties for connection(s) in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Andrew Grandison
 
Posts: n/a

Default Dynammic Properties for connection(s) - 08-11-2004 , 04:13 AM






Hello,

I have a DTS package that performs dozens of data pump tasks.

I have set EACH data pump task up as going from one connection to
another.
This combination of task (con1 -> pumptask -> con2) is duplicated
again and again within the package.

I am using a dynamic properties task to change the connection but need
to know if the workflow properties need to be set for EVERY data pump
task to have a precedence of success of the Dynamic Properties task?
If not, how do I choose which datapump task on which to set the
workflow?

Remember (for what its worth) that I have the package set up this
way:-

con1 -> pumptask1 -> con2
con1 -> pumptask2 -> con2
con1 -> pumptask3 -> con2

rather than

-> pumptask1
con1 -> pumptask2 -> con2
-> pumptask3

Any ideas?

Reply With Quote
  #2  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: Dynammic Properties for connection(s) - 08-11-2004 , 03:44 PM






You don't

The DataSource property is for the connection not a DataPump.

In your example you have 2 connections only.

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know


"Andrew Grandison" <andrewgrandison (AT) hotmail (DOT) com> wrote

Quote:
Hello,

I have a DTS package that performs dozens of data pump tasks.

I have set EACH data pump task up as going from one connection to
another.
This combination of task (con1 -> pumptask -> con2) is duplicated
again and again within the package.

I am using a dynamic properties task to change the connection but need
to know if the workflow properties need to be set for EVERY data pump
task to have a precedence of success of the Dynamic Properties task?
If not, how do I choose which datapump task on which to set the
workflow?

Remember (for what its worth) that I have the package set up this
way:-

con1 -> pumptask1 -> con2
con1 -> pumptask2 -> con2
con1 -> pumptask3 -> con2

rather than

-> pumptask1
con1 -> pumptask2 -> con2
-> pumptask3

Any ideas?



Reply With Quote
  #3  
Old   
Andrew Grandison
 
Posts: n/a

Default Re: Dynammic Properties for connection(s) - 08-11-2004 , 10:35 PM



True, but using the GUI (package designer) I can't set workflow
properties for a connection - only for a data pump. I don't want to
rely on a particular datapump task always being the first to execute
and then linking the dynamic properties task to that task (via
workflow/success).

I must be missing something fundamental here because I can't find any
posts providing info on what to do in this situation.

Thanks


"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote

Quote:
You don't

The DataSource property is for the connection not a DataPump.

In your example you have 2 connections only.

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know


"Andrew Grandison" <andrewgrandison (AT) hotmail (DOT) com> wrote in message
news:1bf3229f.0408110113.31c96139 (AT) posting (DOT) google.com...
Hello,

I have a DTS package that performs dozens of data pump tasks.

I have set EACH data pump task up as going from one connection to
another.
This combination of task (con1 -> pumptask -> con2) is duplicated
again and again within the package.

I am using a dynamic properties task to change the connection but need
to know if the workflow properties need to be set for EVERY data pump
task to have a precedence of success of the Dynamic Properties task?
If not, how do I choose which datapump task on which to set the
workflow?

Remember (for what its worth) that I have the package set up this
way:-

con1 -> pumptask1 -> con2
con1 -> pumptask2 -> con2
con1 -> pumptask3 -> con2

rather than

-> pumptask1
con1 -> pumptask2 -> con2
-> pumptask3

Any ideas?

Reply With Quote
  #4  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: Dynammic Properties for connection(s) - 08-12-2004 , 12:09 AM



Oh Ok

Because you are using 1 Source and 1 destination then then will be executed
serially. The order will I believe be the order in which they were
designed. If you want to explicitly managed who goes when then yes you need
to constrain each DataPump task.

If you do not want to have to figure it out then you could always use
variables to set the connection properties and use a "Starter Package" that
fires your real package and sets the proerties

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know


"Andrew Grandison" <andrewgrandison (AT) hotmail (DOT) com> wrote

Quote:
True, but using the GUI (package designer) I can't set workflow
properties for a connection - only for a data pump. I don't want to
rely on a particular datapump task always being the first to execute
and then linking the dynamic properties task to that task (via
workflow/success).

I must be missing something fundamental here because I can't find any
posts providing info on what to do in this situation.

Thanks


"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote

You don't

The DataSource property is for the connection not a DataPump.

In your example you have 2 connections only.

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know


"Andrew Grandison" <andrewgrandison (AT) hotmail (DOT) com> wrote in message
news:1bf3229f.0408110113.31c96139 (AT) posting (DOT) google.com...
Hello,

I have a DTS package that performs dozens of data pump tasks.

I have set EACH data pump task up as going from one connection to
another.
This combination of task (con1 -> pumptask -> con2) is duplicated
again and again within the package.

I am using a dynamic properties task to change the connection but need
to know if the workflow properties need to be set for EVERY data pump
task to have a precedence of success of the Dynamic Properties task?
If not, how do I choose which datapump task on which to set the
workflow?

Remember (for what its worth) that I have the package set up this
way:-

con1 -> pumptask1 -> con2
con1 -> pumptask2 -> con2
con1 -> pumptask3 -> con2

rather than

-> pumptask1
con1 -> pumptask2 -> con2
-> pumptask3

Any ideas?



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.