remedios_


Hi~,

Before implementing memory based bulk copy insert with IRowsetFastLoad interface of SQL Server 2005 OLE DB provider, I want to know some considerations.

- performance : compared with T-SQL's "BULK INSERT ..." and bcp utility

- SQL Server's resource usage : when running memory based bulk copy, server resource's influence

- server side action(behavior) : when server is busy, delayed-update means IRowsetFastLoad::Commit(true) method can insert right after

- row-count : The rowcount limitation can be inserted by IRowsetFastLoad::InsertRow() method before IRowsetFastLoad::Commit

- any other guide lines





Re: Questions about bulk copy insert using 'Memory Based Bulk Copy Operations'

Waseem Basheer - MSFT


remedios_,

* Bulk insert and bcp work on top of data files. IRowsetFastLoad works from data in memory, that is the main difference. bcp and IRowsetFastLoad are client side implementations, so they have network overhead associated with them but they generate similar format request to the server. If you have data in memory already I would recommend the use of IRowsetFastLoad or bcp API (the in-memory one). If you have data in some files currently, then you can use either bcp executa ble or bcp API (file based) or IBCPSession interface in SQLNCLI OLEDB.

* IRowsetFastLoad or bcp APIs would result in identical memory usage patterns on the server only difference is only how they read data i.e. one from memory and other from file.

I don't understand questions 3 and 4. Can you elaborate a little bit more.

Thanks

Waseem