Performing Bulk Copy Operations (ODBC)
The ODBC standard does not directly support SQL Server bulk copy operations. When connected to an instance of SQL Server version 7.0 or later, the SQL Native Client ODBC driver supports the DB-Library functions that perform SQL Server bulk copy operations. This driver-specific extension provides an easy upgrade path for existing DB-Library applications that use bulk copy functions. The specialized bulk copy support is in the following files:
- sqlncli.h
Includes function prototypes and constant definitions for bulk copy functions. sqlncli.h must be included in the ODBC application performing bulk copy operations and must be in the application's include path when it is compiled. - sqlncli.lib
Must be in the library path of the linker and specified as a file to be linked. sqlncli.lib is distributed with the SQL Native Client ODBC driver. - sqlncli.dll
Must be present at execution time. sqlncli.dll is distributed with the SQL Native Client ODBC driver.
.gif "ms130792.note(de-de,SQL.90).gif") Hinweis: |
|---|
| The ODBC SQLBulkOperations function has no relationship to the SQL Server bulk copy functions. Applications must use the SQL Server-specific bulk-copy functions to perform bulk copy operations. |
Minimally Logging Bulk Copies
With the Full Recovery model, all row-insert operations performed by bulk load are fully logged in the transaction log. For large data loads, this can cause the transaction log to fill rapidly. Under certain conditions, minimally logging is possible. Minimal logging reduces the possibility of a bulk load operation filling the log space and is also more efficient than full logging.
For information on using minimal logging, see Voraussetzungen für die minimale Protokollierung beim Massenimport.
Siehe auch
Konzepte
Andere Ressourcen
Importieren und Exportieren von Massendaten