| title | Cross-Version Compatibility | 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 | |
| helpviewer_keywords |
|
|
| ms.assetid | 5f14850b-b85c-41e2-8116-6f5b3f5e0856 | |
| caps.latest.revision | 14 | |
| author | JennieHubbard | |
| ms.author | jhubbard | |
| manager | jhubbard |
[!INCLUDESNAC_Deprecated]
Cross-version conflicts can occur when client or server instances of [!INCLUDEssNoVersion] earlier than [!INCLUDEssKatmai] are expected to process table-valued parameters.
In general, table-valued parameter functionality is only available to [!INCLUDEssKatmai] clients (using SQL Server Native Client 10.0) or later that are connected to [!INCLUDEssKatmai] (or later) servers. New columns in catalog function result sets will only be present when connected to a [!INCLUDEssKatmai] (or later) server.
If a client application compiled with an earlier version of [!INCLUDEssNoVersion] Native Client executes statements that expect table-valued parameters, the server detects this condition through a data conversion error, and ODBC returns this as a SQLSTATE 07006 and the message "Restricted data type attribute violation".
If a client application that was compiled with [!INCLUDEssNoVersion] Native Client 10.0 or later tries to use table-valued parameters when connected to a server instance earlier than [!INCLUDEssKatmai], [!INCLUDEssNoVersion] Native Client will detect this, and SQLBindCol, SQLBindParameter, SQLSetDescFields, and SQLSetDescRec calls will fail with SQLSTATE 07006 and the message "Restricted data type attribute violation (the version of SQL Server for this connection does not support table-valued parameters)".