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


BCP vs. OPENDATASOURCE


BCP vs. OPENDATASOURCE

Author
Message
Jake
Jake
Forum Newbie
Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)

Group: General Forum Members
Points: 8 Visits: 423
I’m researching some of the different methods of loading the data warehouse via T-SQL. I have some questions.

Which is most efficient/faster, and why?

A. BCP: On source system, export data to flat file. Then load into DW via BCP or Bulk Insert.
Overhead: query data, writing to a flat file, transferring over network, converting flat file data to data types, inserting into a table. DW is simple mode logging, therefore minimal logging is the same as BCP. Other overhead to consider?

B. Distributed Query: Import data from source system via OPENDATASOURCE, running a stored procedure on the source system to run a query to get the data. The data is then inserted in a table in the DW.
Overhead: query data, storing result set temporarily in tempdb, transferring over network, inserting into table. DW is simple mode logging, therefore minimal logging is the same as BCP. OPENDATASOURCE/sp does not allow for batch. To batch, multiple data requests will have to be made to the source system, which adds to overhead. Other overhead to consider?

Where are the large bottlenecks:
Write to flat file vs. write to tempdb?
Network transferring flat file vs. transferring dataset?
Batching flat file with BCP vs. batching multiple calls over OPENDATASOURCE to stored procedure?
Others?

Thank you.



Jeff Moden
Jeff Moden
SSC-Forever
SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)

Group: General Forum Members
Points: 44886 Visits: 39856
SQL Server uses BCP to do replication... that should be the answer right there. And, if you use the NATIVE mode (like replication does), you don't have to worry about datatypes and all that.

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
     Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is usually not.
Just because you can do something in PowerShell, doesnt mean you should. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
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