dbTalk Databases Forums  

Best practice "Transform Data Task"

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


Discuss Best practice "Transform Data Task" in the microsoft.public.sqlserver.dts forum.



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

Default Best practice "Transform Data Task" - 04-05-2006 , 02:28 AM






Greetings experienced DTS people..

I was just wondering, is there a best practice to how many "Transform Data
Tasks" lines you should have between two connections? In your experience,
what is the upper limit before the system performance starts to suffer? 5,
50, 500, 5000?

I'm trying to figure when it is better to add a new connection instead of
adding a new "group" of transform data lines...

Thank you for helping out a newbie!

Cheers,
Elise



Reply With Quote
  #2  
Old   
Enric
 
Posts: n/a

Default RE: Best practice "Transform Data Task" - 04-05-2006 , 10:51 AM






Hi,

Best practices such as allocate an exception file for each PUMP task are
always welcomed as well as set in natural names in each connection rather
than Sql choose for us references such as:
"Microsoft OLE DB Provider for SQL Server 2"
"Microsoft OLE DB Provider for SQL Server"

Moreover such references aren't visible in all their lenght from the design
sheet.
--
Please post DDL, DCL and DML statements as well as any error message in
order to understand better your request. It''s hard to provide information
without seeing the code. location: Alicante (ES)


"Elise" wrote:

Quote:
Greetings experienced DTS people..

I was just wondering, is there a best practice to how many "Transform Data
Tasks" lines you should have between two connections? In your experience,
what is the upper limit before the system performance starts to suffer? 5,
50, 500, 5000?

I'm trying to figure when it is better to add a new connection instead of
adding a new "group" of transform data lines...

Thank you for helping out a newbie!

Cheers,
Elise




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

Default Re: Best practice "Transform Data Task" - 04-05-2006 , 02:42 PM



Hello Elise,

You should create new connections to the data source(s). You should not
have tasks going at the same time than there are processors in the box.
All you will see happen is a lot of context switching and the false appearance
of things going at the same time.

Multiple Transform data tasks between the same two connections. Only one
will go at any one time.



Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Quote:
Greetings experienced DTS people..

I was just wondering, is there a best practice to how many "Transform
Data Tasks" lines you should have between two connections? In your
experience, what is the upper limit before the system performance
starts to suffer? 5, 50, 500, 5000?

I'm trying to figure when it is better to add a new connection instead
of adding a new "group" of transform data lines...

Thank you for helping out a newbie!

Cheers,
Elise



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.