| title | FILESTREAM Support | Microsoft Docs | ||
|---|---|---|---|
| ms.custom | |||
| ms.date | 03/17/2017 | ||
| ms.prod | sql | ||
| ms.prod_service | database-engine | ||
| ms.reviewer | |||
| ms.technology | native-client | ||
| ms.topic | reference | ||
| helpviewer_keywords |
|
||
| ms.assetid | 1ad3400d-7fcd-40c9-87ae-f5afc61e0374 | ||
| author | markingmyname | ||
| ms.author | maghan |
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md]
FILESTREAM provides a way to store and access large binary values, either through [!INCLUDEssNoVersion] or by direct access to the Windows file system. A large binary value is a value larger than 2 gigabytes (GB). For more information about enhanced FILESTREAM support, see FILESTREAM (SQL Server).
When a database connection is opened, @@TEXTSIZE will be set to -1 ("unlimited"), by default.
It is also possible to access and update FILESTREAM columns using Windows file system APIs.
For more information, see the following topics:
Schema rowsets in OLE DB will not report whether a column is a FILESTREAM column. ITableDefinition in OLE DB cannot be used to create a FILESTREAM column.
Catalog functions such as SQLColumns in ODBC will not report whether a column is a FILESTREAM column.
To create FILESTREAM columns or to detect which existing columns are FILESTREAM columns, you can use the is_filestream column of the sys.columns catalog view.
The following is an example:
-- Create a table with a FILESTREAM column.
CREATE TABLE Bob_01 (GuidCol1 uniqueidentifier ROWGUIDCOL NOT NULL UNIQUE DEFAULT NEWID(), IntCol2 int, varbinaryCol3 varbinary(max) FILESTREAM);
-- Find FILESTREAM columns.
SELECT name FROM sys.columns WHERE is_filestream=1;
-- Determine whether a column is a FILESTREAM column.
SELECT is_filestream FROM sys.columns WHERE name = 'varbinaryCol3' AND object_id IN (SELECT object_id FROM sys.tables WHERE name='Bob_01');
If your client was compiled using the version of [!INCLUDEssNoVersion] Native Client that was included with [!INCLUDEssVersion2005], and the application connects to [!INCLUDEssCurrent], varbinary(max) behavior will be compatible with [!INCLUDEssVersion2005]. That is, the maximum size of returned data will be limited to 2 GB. For result values larger that 2 GB, truncation will occur and a "string data right truncation" warning will be returned.
When data-type compatibility is set to 80, client behavior will be consistent with down-level client behavior.
For clients that use SQLOLEDB or other providers that were released before the [!INCLUDEssVersion2005] version of [!INCLUDEssNoVersion] Native Client, varbinary(max) will be mapped to image.