dbTalk Databases Forums  

Serial or Parallel?

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


Discuss Serial or Parallel? in the microsoft.public.sqlserver.dts forum.



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

Default Serial or Parallel? - 01-28-2005 , 06:11 AM






Hi

Hopefully just a quickie.

When just importing tables and their data, is it better to use seperate
source & destination connections for each table, to run the process in
parallel, or to use a "Copy SQL Objects Task" to include all tables?

With the later, I'm thinking that the imports will run serially as there are
only two connections specified.

Any advice from one that knows would be greatly appreciated!

BTW These aren't huge tables, roughly 3 million rows per table.

Cheers

Joe

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

Default Re: Serial or Parallel? - 01-29-2005 , 01:05 AM






Personally I do use seperate connection definitions. If I want to bulk load
I also drop all indexes on the destination first and reapply later.

--



Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


"Joe" <Joe (AT) discussions (DOT) microsoft.com> wrote

Quote:
Hi

Hopefully just a quickie.

When just importing tables and their data, is it better to use seperate
source & destination connections for each table, to run the process in
parallel, or to use a "Copy SQL Objects Task" to include all tables?

With the later, I'm thinking that the imports will run serially as there
are
only two connections specified.

Any advice from one that knows would be greatly appreciated!

BTW These aren't huge tables, roughly 3 million rows per table.

Cheers

Joe



Reply With Quote
  #3  
Old   
Joe
 
Posts: n/a

Default Re: Serial or Parallel? - 01-31-2005 , 03:01 AM



Thanks Allan.

"Allan Mitchell" wrote:

Quote:
Personally I do use seperate connection definitions. If I want to bulk load
I also drop all indexes on the destination first and reapply later.

--



Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


"Joe" <Joe (AT) discussions (DOT) microsoft.com> wrote in message
news:70FA3F79-004C-4E8C-B6E7-D8792FE38B6F (AT) microsoft (DOT) com...
Hi

Hopefully just a quickie.

When just importing tables and their data, is it better to use seperate
source & destination connections for each table, to run the process in
parallel, or to use a "Copy SQL Objects Task" to include all tables?

With the later, I'm thinking that the imports will run serially as there
are
only two connections specified.

Any advice from one that knows would be greatly appreciated!

BTW These aren't huge tables, roughly 3 million rows per table.

Cheers

Joe




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.