BCP vs. OPENDATASOURCE

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » SQL Server 2005 Performance Tuning » BCP vs. OPENDATASOURCE

BCP vs. OPENDATASOURCE

Rate Topic

Display Mode

Topic Options

Author

Message

Jake

Posted Sunday, December 28, 2008 1:15 PM

Forum Newbie

Group: General Forum Members
Last Login: Friday, April 26, 2013 12:14 PM
Points: 6, Visits: 295

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.

Post #626329

Jeff Moden

Posted Sunday, December 28, 2008 2:31 PM

SSC-Dedicated

Group: General Forum Members
Last Login: Yesterday @ 6:33 PM
Points: 32,889, Visits: 26,757

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."

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Post #626342

« Prev Topic | Next Topic »

Permissions