| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | apilocation | apiname | apitype | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
bcp_sendrow |
bcp_sendrow |
markingmyname |
maghan |
03/14/2017 |
sql |
native-client |
reference |
|
sqlncli11.dll |
bcp_sendrow |
DLLExport |
[!INCLUDESQL Server Azure SQL Database Synapse Analytics PDW]
Sends a row of data from program variables to [!INCLUDEssNoVersion].
RETCODE bcp_sendrow (
HDBC hdbc);
hdbc
Is the bulk copy-enabled ODBC connection handle.
SUCCEED or FAIL.
The bcp_sendrow function builds a row from program variables and sends it to [!INCLUDEssNoVersion].
Before calling bcp_sendrow, you must make calls to bcp_bind to specify the program variables containing row data.
If bcp_bind is called specifying a long, variable-length data type, for example, an eDataType parameter of SQLTEXT and a non-NULL pData parameter, bcp_sendrow sends the entire data value, just as it does for any other data type. If, however, bcp_bind has a NULL pData parameter, bcp_sendrow returns control to the application immediately after all columns with data specified are sent to [!INCLUDEssNoVersion]. The application can then call bcp_moretext repeatedly to send the long, variable-length data to [!INCLUDEssNoVersion], a chunk at a time. For more information, see bcp_moretext.
When bcp_sendrow is used to bulk copy rows from program variables into [!INCLUDEssNoVersion] tables, rows are committed only when the user calls bcp_batch or bcp_done. The user can choose to call bcp_batch once every n rows or when there is a lull between periods of incoming data. If bcp_batch is never called, the rows are committed when bcp_done is called.
For information about a breaking change in bulk-copying beginning in [!INCLUDEssVersion2005], see Performing Bulk Copy Operations (ODBC).