| title | SQLNumResultCols | Microsoft Docs | |
|---|---|---|
| ms.custom | ||
| ms.date | 03/14/2017 | |
| ms.prod | sql-server-2016 | |
| ms.reviewer | ||
| ms.suite | ||
| ms.technology |
|
|
| ms.tgt_pltfrm | ||
| ms.topic | reference | |
| apitype | DLLExport | |
| helpviewer_keywords |
|
|
| ms.assetid | f79d8b3c-521e-4e50-a564-21d73ae5767b | |
| caps.latest.revision | 33 | |
| author | JennieHubbard | |
| ms.author | jhubbard | |
| manager | jhubbard |
[!INCLUDESNAC_Deprecated]
For executed statements, the [!INCLUDEssNoVersion] Native Client ODBC driver does not visit the server to report the number of columns in a result set. In this case, SQLNumResultCols does not cause a server roundtrip. Like SQLDescribeCol and SQLColAttribute, calling SQLNumResultCols on prepared but not executed statements generates a server roundtrip.
When a [!INCLUDEtsql] statement or statement batch returns multiple result row sets, it is possible for the number of result set columns to change from one set to another. SQLNumResultCols should be called for each set. When the number of columns changes, the application should rebind data values prior to fetching row results. For more information about handling multiple result set returns, see SQLMoreResults.
Improvements in the database engine starting with [!INCLUDEssSQL11] allow SQLNumResultCols to obtain more accurate descriptions of the expected results. These more accurate results may differ from the values returned by SQLNumResultCols in previous versions of [!INCLUDEssNoVersion]. For more information, see Metadata Discovery.