| description | Executing Catalog Functions | ||
|---|---|---|---|
| title | Executing Catalog Functions | Microsoft Docs | ||
| ms.custom | |||
| ms.date | 01/19/2017 | ||
| ms.prod | sql | ||
| ms.prod_service | connectivity | ||
| ms.reviewer | |||
| ms.technology | connectivity | ||
| ms.topic | conceptual | ||
| helpviewer_keywords |
|
||
| ms.assetid | c59cbda3-e214-4399-9edc-cfac86b378d7 | ||
| author | David-Engel | ||
| ms.author | v-daenge |
Because a catalog function creates a result set, it is equivalent to executing any result set-generating SQL statement. In fact, catalog functions are often implemented by executing predefined SQL statements or calling predefined procedures that are shipped with the driver or DBMS. Almost anything that applies to SQL statements that create result sets also applies to catalog functions. For example, the SQL_ATTR_MAX_ROWS statement attribute limits the number of rows returned by the catalog function, just as it limits the number of rows returned by a SELECT statement.
To execute a catalog function, an application just calls the function.
For more information about catalog functions, see Catalog Functions.